Linked by Kroc Camen on Sat 29th May 2010 20:41 UTC
Apple I've been meaning to write this for some time, and for all the time I delayed the more poignant the point I wanted to make started to become as new news came out further solidifying my angle. When I begun writing this article the iPad had not yet been revealed, iPhone OS 4 was not on the map and Apple had not yet purchased Lala. You've probably just noticed that all of these events in fact point toward Apple embracing the web more and in this article I will point out why this is not the case because I believe Apple's agenda here is similar to something we've already seen in recent history.
Thread beginning with comment 427183
To read all comments associated with this story, please click here.
Er
by Beta on Sat 29th May 2010 23:43 UTC
Beta
Member since:
2005-07-06

Completely rational article, if lacking Apples attempt to block competition by adopting obviously patented tech.
But I have issue with one line:

How could the web gain the abilities of native apps? The technology really isn’t that far away!

However much one may dislike Java for [speed / development clunkliness / binary size / etc], it has existed for over a decade and has given the Web native apps to run locally… and it’s already available on an insane amount of platforms and architectures.
Bit sad the Haiku OpenJDK port hasn’t got anywhere, yet, but it will.

Humorously though, while it isn’t mentioned in the article, it’s relevant - Apple has done the same as Microsoft did a decade ago, controlling the JVM - Apple keep the JVM under their control by shipping it themselves and holding back updates by years.

Reply Score: 4

NaCl is not Java (or ActiveX)
by dpJudas on Sun 30th May 2010 05:55 in reply to "Er"
dpJudas Member since:
2009-12-10

NaCl is an attempt at creating a new binary interface between applications and the operating system.

Do not see it as trying to be another Java, but rather as a replacement for PE (Windows) and ELF (Linux) executables. The main difference is that the syscalls for Unix and Windows was designed in a time and age where a system had a system administrator that knew what he was doing. The syscalls in NaCl are far more defensive in nature and are not using the root user mentality that both Unix and Windows has shown to not work well for personal computers.

While you can rightfully argue that applets and the Java VM attempted to deliver the same thing, the way it is being done is significantly different. The NaCl design is not tied to a specific language, but aims at allowing any compiler that can target Windows+Unix today to target it by just adding another target to the compiler.

This is a significant difference since it will allow you to recompile a typical well-written cross platform C language family application with fairly little effort. Both Java (and Silverlight) suffer from the problem that their sandboxes are tightly married to the languages they were designed for and unfortunately have design decisions that make them unsuitable for languages not designed for them. NaCl will finally allow you to write your applications in the language of your choice and not something Javascript, Java, C# or any other language for that matter.

Those that think of NaCl as another ActiveX are also mistaken, since ActiveX allowed you to use the Windows syscalls - something that was a very, very bad idea.

Reply Parent Score: 1

moondevil Member since:
2005-07-08

What a piece of nonsense!

NaCL is only providing a portable way to move C and C++ applications to the browser, but only if the applications only use one of the already ported applications.

And most likely a Chrome only solution.

Java and .Net world already support this for ages now, and what "married to the languages" mean?

JVM:

Java, Scala, JRuby, Jython, Jacl, Jaskel, Groovy, ...

.Net:

C#, VB.Net, JSCript.Net, C++/CLI, F#, Axum, IronRuby, IronPyhon, Powershell, ...

JavaFX:

JavaFX language, plus all the JVM ones

Silverlight:

C#, VB.Net, JSCript.Net, IronRuby, IronPyhon, F# (unofficially), C++/CLI might be possible in the future for pure CLR code.

The only thing in common all these runtimes provide is that there is nothing to see here for C/C++ fan boys, languages that I do like very much, but are the source of the majority of security issues we have to suffer nowadays.


So, I honestly don't see the goals of NaCl, besides being Google own plugin solution.

Reply Parent Score: 4