News for hackers. Stuff that matters.
Re:Google Introduces Portable Native Client by pekk on Saturday May 18, 2013 @02:22AM (#5728081)
If you think this kind of technology compares to Google Reader, you are just confused. WebGL would be a better comparison.
Re:Google Introduces Portable Native Client by coldtea on Saturday May 18, 2013 @03:04AM (#5728128)
Only WebGL is a standard, whereas PNaCL is a Google only endeavor. If it doesn't catch up, they might abandon it just as they did anything else of theirs.

Whereas they cannot abandon WebGL if they want to have a standards compliant browser.

Re:Google Introduces Portable Native Client by TheZenPsycho on Saturday May 18, 2013 @04:39AM (#5728283)
Actually google doesn't seem to have much problems with abandoning standards lately.
Re:Google Introduces Portable Native Client by TazeTSchnitzel on Saturday May 18, 2013 @09:17AM (#5728790)
Perhaps Google's O3D, their 3D graphics implementation in the browser, which you haven't heard of. Why? Because when WebGL beat it, it was dropped.
Re:Google Introduces Portable Native Client by mratzloff on Saturday May 18, 2013 @12:41PM (#5729497)
At least Google released a final version of O3D that was an implementation on top of WebGL, providing a transition path. When they dropped Gears, they said they said,

We realize there is not yet a simple, comprehensive way to take your Gears-enabled application and move it (and your entire userbase) over to a standards-based approach. We will continue to support Gears until such a migration is more feasible...[1]

How did that turn out?

They filed a Chromium ticket[2] that was moved to an html5rocks.com ticket[3] four months later that was closed as WONTFIX a month after that.

My issue is not that they discontinue projects. My issue is how they often go about it.

[1] http://gearsblog.blogspot.com/2010/02/hello-html5.html [2] http://code.google.com/p/chromium/issues/detail?id=37180 [3] http://code.google.com/p/html5rocks/issues/detail?id=73