Sign up ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

As some of you may know already, Google Native Client is going to be released with Chrome 14. Google native client is a technology that allow us to run native code(C, C++) on the web. (Cross-browser). I heard it's pretty secure as well.

Is it the end of client/server side programming? The end of javascript, php,, ruby, jsp etc.???

It seems google native client has the potential to change the game. What do you think?

share|improve this question

closed as not constructive by Mark Trapp Aug 12 '11 at 14:53

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Google Wave had the potential to change the game, too. Wait and see. –  Caleb Aug 12 '11 at 13:28
Yet another example of technology going around in circles. Same patterns, different names. –  quant_dev Aug 12 '11 at 13:45
Look at Google+ boom, anything could happen... –  Jasson Aug 12 '11 at 13:56
Hi Jasson, idle speculation is not on-topic here because it invites extended discussion. Is there a specific, practical problem you need help with? If so, feel free to ask about that. –  user8 Aug 12 '11 at 14:54

4 Answers 4

Google has a lot of cash to spend throwing things at the wall and seeing what sticks. Nothing wrong with that, it is very nice to see innovation no matter how interesting or weird. But for enterprises to adopt such things it takes time, lawyers get involved, and just because something looks "cool" does not immediately translate into widespread adoption.

share|improve this answer

I assume Google wants to expand capability of the Chrome Browser instead of their operating system ChromeOS.

The disadvantage of Chrome OS is, that it is almost nothing without Internet connectivity. iThat may change with programs and or libraries, that are implemented as "Google Chrome Native Client".

Even without considering the speed of Javascript/HTML compared against a native C application: There are and will be a lot of programs that people are not willing to translate from existing C-Code to Javascript/HTML. Providing the native client a lot of code will become reusable inside a browser, which runs on any platform. That may draw some attention to C developers.

Regarding these two points, I think it is the logical step for Google to establish Chrome OS with Chrome browser as a real platform. Why don't they just set up another operating system? Have a look at Apple, Linux and Microsoft: All programs that run exclusively on one platform, are a reason to stay with the OS of your choice. But installing a web browser, if you not already have, can not be considered as "leaving your OS". You can continue using your system of choice, and still be able to use Chromes features.

So I do think that client/server programming may change a bit, however rendering hypertext and processing user input on server-side will still be a thing we stay with a long time:

  • native client applications will not run in Firefox / IE which still have an immense market share together

  • processing user input can only reliably done on a server, there is no reason to trust data from a native client more than data entered in a standard HTML form or browser.

  • submitting user data to any kind of central storage will still take the need of verification and further processing (correcting, transforming, reporting)

share|improve this answer
Why don't they just set up another operating system? I think that is the ultimate goal. To have an operating system that runs on everyone else's, and on occasion by itself. With out the pain of a VM. It's especially nice that this OS pushes Google products oh-so elegantly... –  Jeremy Heiler Aug 12 '11 at 14:41

Server-side is not only about "where to run code", it is also about security. Would you store the passwords of all your users in a cookie? Much safer on a database where you can control the access.

So no, it is not the end of server-side programming, I doubt it will change the game much. The game will get faster, probably.

share|improve this answer

The thing with Google's NaCl is performance. No matter how hard you try HTML is intepreted and slow. Do you imagine building complex flash-like or silverlight-like animations for, say, reporting with HTML 5?

Google needs performance for its Chrome family (specially Chrome OS) and NaCl is a good approach. Obviously Server Side Programming and Middleware can't dissapear but get NaCl + XmlHttpRequest and you'll get faster experiences.

Now, there's seems to be some concerns about be again using C and C++, but I'm confident NaCl will end supporting other options like marvelous Google's Go!

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.