[unconed]

"And now we've taken this canvas, and hooked it up to a modified version of OpenGL ES!" Only it turns out that neither Apple nor Microsoft trust their "superior" native drivers enough to let the open web talk to it, even through a completely type-safe and memory-managed interface.

Different constraints, different security model, different applications. But the fact that triple A games still routinely crash on Windows is enough of an indicator that the security and stability of native code is highly overrated.

[WayneDB]

And what triple A games are even written in HTML/JS?

If native isn't up to the task, then HTML/JS certainly ain't because HTML/JS is hosted in a browser that runs natively. That was his whole point.

Furthermore, I have witnessed hundreds of different "top sites" that simply don't work in all sorts of browsers. The typical response from web devs is, "They probably built it wrong." Well, I suppose you can apply the same logic to your triple A games example. (Popularity may not be due to any one type of quality. Look at Minecraft.)

[unconed]

"Native code's benefits are overrated" is not the same as "HTML is superior!". Like I said, different constraints, different requirements.

But, when a native app crashes, it usually means an exploit waiting to happen. When a browser renders something wrong... it renders something wrong. You close the tab and move on.