User: Password:
Subscribe / Log in / New account

Yet more lock-in to X86

Yet more lock-in to X86

Posted Jun 4, 2009 12:33 UTC (Thu) by addw (guest, #1771)
Parent article: Google's Native Client

The first thought that I had was what about people who want to use other hardware ? Most of the desktop world seems to be Intel compatible at the moment, but I can see that this will change - ARM looks like it will take some space.

I don't like the idea at all.

(Log in to post comments)

Yet more lock-in to X86

Posted Jun 4, 2009 21:04 UTC (Thu) by jimparis (guest, #38647) [Link]

Agreed, people should take all this NaCl stuff with a grain of salt :)
I thought the "this plugin works only on x86" mentality was beaten to death years ago. Glad to see Google's picking up the slack and making the web suck again...

Yet more lock-in to X86

Posted Jun 5, 2009 23:54 UTC (Fri) by vomlehn (subscriber, #45588) [Link]

Not only no to NaCl, but hell, no. We're just on the cusp of cracking the Microsoft operating system monopoly and we're going to shore up Intel's processor monopoly? We are definitely getting into the evil zone, here. It's pretty hard to compete on price with a company that dominates the market but, from the technical standpoint, Intel's power consumption and die size are way greater than comparable RISC processors. Hardly Green technology.

Java was developed from the ground up to be verified and it does the job darn well. I'm starting to see benchmarks where it goes toe to toe with C, once you are done with JITting the code. It's well proven and platform-independent. Please, Google, let's stick with something that is already working. And, of course, if you want to spend time and money making Java run faster, that would not be evil.

Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds