Mozilla’s Rejection of NativeClient Hurts the Open Web
Update: To avoid potential confusion, I will plainly state my overall thesis. The primary benefit of the internet is its openness, connectedness, standardness. By not adopting a technology capable of...
View ArticleClik here to view.
Digging Into JavaScript Performance
While JavaScript implementations have been improving by leaps and bounds, I predict that they still won’t meet the performance of native code within the next couple years, even when plenty of memory is...
View ArticleNative Client is Widely Misunderstood (And What Google Should Do About It)
Wow. My recent post about why Mozilla should adopt Native Client stirred up quite a storm. Some folks don’t believe the web needs high-performance applications. Some are happy with whatever APIs...
View ArticleIn Defense of Language Democracy (Or: Why the Browser Needs a Virtual Machine)
Years ago, Mark Hammond did a bunch of work to get Python running inside Mozilla’s script tags. Parts of Mozilla are ostensibly designed to be language-independent, even. Unfortunately, even if Mozilla...
View ArticleDigging into JavaScript Performance, Part 2
UPDATE. After I posted these numbers, Alon Zakai, Emscripten’s author, pointed out options for generating optimized JavaScript. I reran my benchmarks; check out the updated table below and the script...
View Article
