4 ms·

...if only Java in the browser wouldn't have failed so bad (and it did long time ago, Apple's decision is just a sad reminder of this), we would actually have t

by nnq 14y ago

...if only Java in the browser wouldn't have failed so bad (and it did long time ago, Apple's decision is just a sad reminder of this), we would actually have the "nirvana" of using Python (Jython), Ruby (JRuby), Clojure and more IN THE BROWSER! Same language on the server and in the browser, even on mobile, and the ability for every developer/team to CHOOSE that language from a few option that run on the JVM... (I know we'll have this one day, with languages that compile to Javascript, but... it could have so much more beautiful, another lost "alternate reality", like the ones in which Lisp went mainstream and even OSs were build in it... sigh...) How dump could Sun and Oracle (I know, the browser Java fight was maybe already lost when Oracle came in...) be not to realize the potential ecosystem that could grow around this? Sigh...

tonyedgecombe 14y ago
Microsoft and Apple have to bear some of the responsibility for this as well.
- nnq 14y ago
  Microsoft, yes, it really made sense for them to be as hostile as possible to Java on all fronts. But Apple? Weren't their Java related decisions too late in the Game to change anyth?...
Kerrick 14y ago
Native Client is the next hope for Python, Ruby, etc. in the browser. Much better than trying to compile an existing language to JavaScript. https://developers.google.com/native-client/ https://developers.google.com/native-client/
- nnq 14y ago
  Hmm... I just can't imagine either Ms or Apple being friendly towards NaCl as it would basically be a way of drilling more wholes into their boats (like competing with Silverlght or the broader "issue" that webifying desktop and mobile apps would risk making iOS or Windows irrelevant and welcome in even more low-cost Android and Linux solutions... every Desktop/iOS app to browser app transition basically makes these guys loose money one way or another...)
- bzbarsky 14y ago
  As long as you're willing to tie your compiled code to particular hardware, sure. The benefit of compiling to JS is that it will Just Work for users as long as they have a web browser, without you having to put up "Oh, get a different hardware device" message.
Sandman 14y ago
There are several projects that attempt to implement JVM in JavaScript. Doppio [1] seems to be the most mature one. So, we may yet see JVM-based languages in the browser (and without the need for a plug-in). [1] http://int3.github.com/doppio/about.html http://int3.github.com/doppio/about.html

by nnq 14y ago

tonyedgecombe 14y ago

Microsoft and Apple have to bear some of the responsibility for this as well.

nnq 14y ago
Microsoft, yes, it really made sense for them to be as hostile as possible to Java on all fronts. But Apple? Weren't their Java related decisions too late in the Game to change anyth?...

Kerrick 14y ago

Native Client is the next hope for Python, Ruby, etc. in the browser. Much better than trying to compile an existing language to JavaScript. https://developers.google.com/native-client/ https://developers.google.com/native-client/

nnq 14y ago
Hmm... I just can't imagine either Ms or Apple being friendly towards NaCl as it would basically be a way of drilling more wholes into their boats (like competing with Silverlght or the broader "issue" that webifying desktop and mobile apps would risk making iOS or Windows irrelevant and welcome in even more low-cost Android and Linux solutions... every Desktop/iOS app to browser app transition basically makes these guys loose money one way or another...)
bzbarsky 14y ago
As long as you're willing to tie your compiled code to particular hardware, sure. The benefit of compiling to JS is that it will Just Work for users as long as they have a web browser, without you having to put up "Oh, get a different hardware device" message.

Sandman 14y ago

There are several projects that attempt to implement JVM in JavaScript. Doppio [1] seems to be the most mature one. So, we may yet see JVM-based languages in the browser (and without the need for a plug-in). [1] http://int3.github.com/doppio/about.html http://int3.github.com/doppio/about.html