Comments on: Google's answer to Java, Flash, Windows: Native Client
The Internet giant announced an open-source project to dramatically boost the power of Web applications. Native Client lets Web apps run with PC power.
The Internet giant announced an open-source project to dramatically boost the power of Web applications. Native Client lets Web apps run with PC power.
Web sites launch all the time, but they also shut their doors. We highlight 15 that bit the dust this year.
Let the debate begin: Was the iPhone more important than iTunes? Was anything bigger than Google finding a great business model? CNET offers its list of the 10 most important stories of the '00s.
Your destination for the latest news on enterprise-level information technology, from chip research and server design to software issues including programming, open source and patents.
Add this feed to your online news reader
all platforms already have the ability to have native apps that can communicate over networks
this is all retarded platforming.
we don't need more platforms, we need apps that are built for the OS we run, and that if needed happen to communicate remotely
Flash is usually avoided there too, but an enterprise will still stump for a license here and there for internal streaming media.
Java OTOH is alive and well in the enterprise. Most high-end and heavy web apps (Google, etc) use it very heavily.
"Java OTOH is alive and well in the enterprise. Most high-end and heavy web apps (Google, etc) use it very heavily. "
It's also highly exploitable and insecure, which is another reason why enterprises are loath to have Java on their network systems as well.
All of them have issues. Google's past record of leaving things in beta, lack of support, and draconian control over content will not help them here.
I love Google, but I'd rather they concentrate on what they're good at, and not continue to spread themselves too thin...
Bleah.
(unless you think that the old System 7 UNIX is the only OS that should exist lest we 'fragment' the OS space...)
"(unless you think that the old System 7 UNIX is the only OS that should exist lest we 'fragment' the OS space...) "
I was actually leaning more towards IRIX, or perhaps something running on a CBM :)
Here's what I don't get -- Adobe and MS are already working on platforms (Flash, Silverlight) that have (or will soon have) a presence on all major browsers and OSes, and will be capable of running fully function applications inside a browser. And managed code is the way ahead for web apps -- easier to develop for, more secure, able to hide architecture details.
So what's Google even thinking with this approach?
1) Whats about none x86 platforms - mobile files etc. What about x64?
2) There is a reason that Java and .Net work the way they do - managed code in a sandbox. This starts to sound a lot like ActiveX controls to me. Do I really want native code launched in my browser. Nope.
3) What "platform" is exposed to the native code? It is OS specific, or what? Again, Java's VM (and also Silverlight) are cross platform.
What is this NativeClient's unique benefit? Its not at all clear.
This does actually make sense, to give full access to a virtual machine, so apps can write to a HD, and you can transfer between them at *your* desire, not the apps desire.
Facebook Connect crashes Firefox half the time and gets identified as a phishing site since it is not coded by Facebook. Developers have to use the libraries and hook it together themselves. This got Facebook blocked for phishing last week.
Not to mention most of these open in new windows and popup blockers will not open the new windows. What a freakin mess they have all made of what could have been really cool.
- by kapil561 January 9, 2009 3:51 AM PST
- How is this different from Google Gears, i mean the goal is the same, isnt it. what am i missing.
- Like this Reply to this comment
-
(36 Comments)