Hacker News Reader

Comment by wwalker3 | Hacker News Reader

Once technologies like Google's Native Client take off, the web browser becomes merely the installer and updater for my native app.

And it'll be none too soon -- then we can abandon the doomed effort to somehow cobble together huge, powerful apps like Maya and Photoshop out of a mess of JavaScript and XML.

View on HN

>> "then we can abandon the doomed effort to somehow cobble together huge, powerful apps like Maya and Photoshop out of a mess of JavaScript and XML."

Or, you know, we could develop better tools for the web.

I'm amazed that this discussion always takes the stance that we're stuck with what we're using for web development now, as if nobody could possibly develop better languages and tools for web use.

That's exactly my point -- NaCl would make languages and tools available to web app developers which have already proven their worth in developing complex, graphically intense application interfaces on the desktop.

That makes no sense to me. Google Native Client is just a desperate attempt to hide expensive code from other companies. How many nuclear power plants, switches, routers, undersea pipelines, servers and UPS systems are needed to run a Facebook turd-app connected to Google DRM anyway ? Talking about the slowness of Javascript is amusing when 856 sub-systems needs to be operational for a Web 2.0 "Hello World".

Give me a break. Americans have no cash and live on credit, thereby creating a marked for AT/T, McDonald's and Google.

That makes no sense to me. What does everything after the second sentence have to do with NaCl?

Perhaps you're replying to a different comment than the one I made? I was talking about the difficulty of creating complex, responsive user interfaces in JavaScript. NaCl (if it works out) seems to open another path for developing interface-heavy apps for the web.

Reply on news.ycombinator.com