Chrome 14 Beta Integrates Native Client

derGoldstein writes "This year Microsoft kept signaling that it's going back to lower-level code with a C++ renaissance. It would give C++ programmers the same priority that was, up until now, reserved for .Net programmers. They even launched a new show about it on their Channel9. Now Google wants to appeal to native programmers with their Native Client for Chrome. It seems the two companies want to cover both the higher-level JavaScript and lower-level C/C++. I dare hope this will give seasoned C/C++ programmers a place alongside JavaScript programmers at the web development table."

Comments

Re:C++ Making its way to the web?

[YodasEvilTwin]

There is no native client standard. They can't break compatibility by adding completely new features unrelated to anything else. They'll just result in web games etc. that only work in Chrome. It's like saying that Apple is "breaking compatibility" by making apps that don't work in Windows.

Re:C++ Making its way to the web?

[shutdown -p now]

The original ActiveX in IE was designed with practically complete disregard for security. NaCl is the opposite of that - it's a very cleverly designed sandbox for native code.

Re:Yeah, I'm so excited

[shutdown -p now]

I suggest that you read about how NaCl actually works before commenting. It is a sandbox for native code. It doesn't run just any code, either - there are certain constraints in place which make it possible to verify the result for safety. "Safety" here means that code cannot break out of the sandbox - it can, of course, still crash itself, but that would be fully isolated, and cannot be used in the usual manner as a privilege escalation exploit.