News for hackers. Stuff that matters.
Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @02:22PM (#3361893)
> JavaScript is locked in. It's too entrenched, it's never going away. Let's just accept that.

JavaScript doesn't have to go anywhere, it can run on a shared VM like any other language.

> That means that adding additional languages creates a burden. You're now supporting, at minimum 2 VMs. If you're going to support a second VM you better get it positively right. That doesn't proclude doing it, it just means it's not coming tomorrow.

There is literally zero investment in moving such an idea forward on the part of Mozilla and WebKit (sans Google). In fact, there's active resistance, while at the same time strongly favoring JavaScript as the one option.

The position more seems to be "we might chip in if someone else comes up with the perfect answer" rather than "yes, this is a problem that needs to be solved to improve developer productivity, application quality, and help the web compete with other platforms".

Re:Why don't they implement Python and Ruby on the web brows... by MatthewPhillips on Friday December 16, 2011 @02:50PM (#3362015)
> JavaScript doesn't have to go anywhere, it can run on a shared VM like any other language.

True, but the JS VMs we have today have been refined over 15+ years and switching to another risks breaking the web in profound ways. Even Google would be against dropping V8 for JS use.

>There is literally zero investment in moving such an idea forward on the part of Mozilla and WebKit (sans Google). In fact, there's active resistance, while at the same time strongly favoring JavaScript as the one option.

>The position more seems to be "we might chip in if someone else comes up with the perfect answer" rather than "yes, this is a problem that needs to be solved to improve developer productivity, application quality, and help the web compete with other platforms".

I read the mailing list and that's not the impression I get at all. The impression I get is:

1) JavaScript still has a lot of room for improvement. Putting resources in an alternative (whatever shape that might take) distracts from improving JavaScript.

2) Most of the problems people have with JavaScript are being addressed by EmcaScript.next.

3) For those who have a general syntax/style problem, there are numerous alternatives that compile to JS to choose from, and more are likely to become popular in future as programmers from different backgrounds are compelled to write for the browser.

Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @03:08PM (#3362096)
> True, but the JS VMs we have today have been refined over 15+ years and switching to another risks breaking the web in profound ways. Even Google would be against dropping V8 for JS use.

And yet, Google, Apple, AND Mozilla have all successfully introduced entirely new or significantly refactored VMs in the past few years.

This is solvable; it HAS been solved.

> JavaScript still has a lot of room for improvement. Putting resources in an alternative (whatever shape that might take) distracts from improving JavaScript.

This doesn't seem contrary to what I've stated above; it's an argument in favor of JavaScript over investing in a generic VM that would open up the ability to develop new browser languages to everyone.

In that regard, failing to allow others to implement custom/experimental languages seems counterproductive to the ultimate goals you seem to be stating here.

> For those who have a general syntax/style problem, there are numerous alternatives that compile to JS

In terms of performance, debugging, profiling, and simple functionality, compiling to JS is simply a work-around, not a solution.

Re:Why don't they implement Python and Ruby on the web brows... by MatthewPhillips on Friday December 16, 2011 @04:03PM (#3362304)
> And yet, Google, Apple, AND Mozilla have all successfully introduced entirely new or significantly refactored VMs in the past few years.

Yes, because the old VMs were critically slow. Things like DOM manipulation aren't blocking problems the way they used to be.

> This is solvable; it HAS been solved.

Why? What critical problem requires a bytecode VM? Developers refusing to write in anything but their favorite language?

> In terms of performance, debugging, profiling, and simple functionality, compiling to JS is simply a work-around, not a solution.

This is solvable without alternative VMs. WebKit is working on CoffeeScript/other language debugging: http://www.infoq.com/news/2011/08/debug-languages-on-javascr...

Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @04:19PM (#3362387)
> Why? What critical problem requires a bytecode VM? Developers refusing to write in anything but their favorite language?

Your argument was that it wasn't technically achievable because it would break the web, yet it's clear that it can be done and HAS been done.

I'll try to address this new argument.

JS isn't perfect, it will never be perfect, and the lack of a bytecode VM is a hindrance to experiments and production language implementations that can lead to better solutions for developers.

Look at the language design that has occurred elsewhere. I may not use Erlang, but I learned a lot from it. Clojure introduced a ton of interesting concurrency constructs (among other advances). C# demonstrated LINQ, and F# is OCaml revisited.

In all of these cases it has nothing to do with whiny developers "refusing to write in anything but their favorite language". We're simply attempting to advance the state of the art, because nothing is perfect, especially JavaScript.

> This is solvable without alternative VMs. WebKit is working on CoffeeScript/other language debugging:

It's a work-around, not a solution. JavaScript still isn't an efficient bytecode format, this won't solve performance issues. We've seen similar work on languages that compile down to C, and it's not an adequate solution to debugging, especially when the debuggers benefit from language-specific enhancements.

Re:Why don't they implement Python and Ruby on the web brows... by jasonlotito on Friday December 16, 2011 @05:28PM (#3362620)
Excuse my ignorance, but what browser-based non-JS VM was introduced successfully? You mentioned this was done before, and I assume you mean it was done successfully, so just curious to know which one it is?
Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @05:42PM (#3362667)
We were actually discussing JS VM replacement in the browser, related to:

> True, but the JS VMs we have today have been refined over 15+ years and switching to another risks breaking the web in profound ways.

The counter-point being that all the major browser vendors have swapped out their VM or performed significant rewrites in the past few years; it's clear that it's possible to implement a new VM and not "break the web in profound ways".

Re:Why don't they implement Python and Ruby on the web brows... by jasonlotito on Friday December 16, 2011 @05:49PM (#3362692)
I think you are misreading that quote. It's not replacing a JS VM with another JS VM that's a problem, it's replacing a JS VM with a non-JS specific VM would cause problems and break the web (something that has been proven to happen).

Arguing that you can replace a JS VM with a JS VM doesn't help the case of replacing a JS VM with a non-JS VM.

Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @07:09PM (#3362903)
At the surface level, I could see how your position would appear logical.

However, the nature of the replacement VM doesn't really matter in the context of what we're describing here.

The problems of compatibility remain the same regardless of whether the target VM is a JS-specific VM, or a general purpose VM; reliance on undefined behavior, accidental changes in semantics, optimization bugs, and so on.

If browser makers were able to swap-out the VM, they've already demonstrated the ability to solve the exact same kind of compatibility problems they'd face here.

Re:Why don't they implement Python and Ruby on the web brows... by bad_user on Friday December 16, 2011 @09:12PM (#3363148)
There is no such thing as general purpose VM.
Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @09:19PM (#3363164)
A VM that provides a standardized bytecode and execution model capable of executing most modern dynamic and static turing complete languages with sufficient performance. This requires more general facilities for common functionality required; refer to tail call support, JVM's invokedynamic, etc.

Or, shorthand, a general purpose browser VM.

Unless, of course, you're arguing that the above is not truly possible, in which case I'd argue that's exactly what Google is exploring via PNaCL, and has (if not completely efficiently) been implemented across existing VMs. The PNaCL choice of LLVM bitcode was likely in error, but regardless, "no such thing" is a stretch.

Re:Why don't they implement Python and Ruby on the web brows... by bad_user on Friday December 16, 2011 @09:34PM (#3363191)
I'm not saying that it is impossible as clearly there have been good efforts being made. However there is no such thing implemented.
Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @09:47PM (#3363212)
Which comes full circle to my original point, which is that other than Google, nobody with a vested interest is trying, and worse yet, they actively oppose progress on this front.
Re:Why don't they implement Python and Ruby on the web brows... by maximusprime on Friday December 16, 2011 @02:26PM (#3361908)
> JavaScript doesn't have to go anywhere, it can run on a shared VM like any other language.

JS running on a general VM would be slower. That's against the interests of the user.

People should stop caring what language it is. If you really don't have the skill required to use Javascript, use something easier for you and get it to compile to JS.

I've really never understood developers that bitch and whine about programming languages all day.

Adding alternate languages to the browser does absolutely nothing for the user. It would only be there to appease the "I shall only develop in lisp" extremist developers.

Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @02:31PM (#3361931)
> JS running on a general VM would be slower. That's against the interests of the user.

What do you base this on? It's sounds like an unsupported assumption regarding the complex technical constraints involved in implementing a general purpose VM and JIT.

Putting the technical specifics aside, intuitively, why would the general VM be slower, especially since the requirement to support JavaScript would be obvious to everyone involved from day 1?

Re:Why don't they implement Python and Ruby on the web brows... by azakai on Friday December 16, 2011 @04:25PM (#3362402)
>> JS running on a general VM would be slower. That's against the interests of the user.

> What do you base this on? It's sounds like an unsupported assumption

No, he is entirely correct.

JavaScript and most dynamic languages do not run at full speed on static-language VMs like the JVM and .NET. This is despite tremendous efforts and motivation to run those languages quickly on such environments, see for example Microsoft's SPUR paper and everything it has done in the CLR to speed up dynamic languages.

The fact is, despite all those efforts, even Microsoft did not implement JS on .NET in IE. This despite Microsoft more than anyone having the capability and moreso the motivation ("everything on .NET"). Microsoft gave up and implemented a new JS engine in native code, and it made that new native JS VM a peer of .NET in Windows 8.

The reasons for this are technical: We do not know how to make a single VM that runs all languages quickly. It's very difficult to do! Dynamic languages need hand-crafted PICs for example, which are extremely difficult to make portable and safe, which is necessary for a VM on the web. Also, low-level details like even how to implement numbers are significant: NaNboxing for example is used in most JS engines, but it probably doesn't make sense in a static language VM. Having both NaNboxed numbers and 'normal' ones in one VM is cumbersome and complex.

Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @04:43PM (#3362458)
> JavaScript and most dynamic languages do not run at full speed on static-language VMs like the JVM and .NET. This is despite tremendous efforts and motivation to run those languages quickly on such environments, see for example Microsoft's SPUR paper and everything it has done in the CLR to speed up dynamic languages.

I'd argue the opposite regarding tremendous efforts and motivation; dynamic languages were an after-thought for both the JVM and .NET, and on the JVM side you've only seen any attempts to improve performance recently, with invokedynamic for Java 7.

The investments here occurred long after the VMs were developed.

> The reasons for this are technical: We do not know how to make a single VM that runs all languages quickly.

The same applies to compilers across the board; we do not know how to make a compiler that applies all possible optimization available to code always, either. I still have to manually vectorize critical paths, re-order code (sometimes in C!) to help the compiler avoid pipeline stalls, etc.

Instead, we do the best general purpose job we can, and it's usually more than fast enough.

What we're talking about here is a VM that has JS support as its first-order target. Using the JVM and CLR as performance examples here -- given what they were built for, and when -- is not particularly valid.

Speaking to NaN-boxing in particular; it's one solution to the problem, but not the only one. I'm going to remain unconvinced here, given that dynamic languages have almost always been a late, second-tier concern for anyone investing serious R&D in the development of a VM/JIT/compiler.

All that said ...

> The fact is, despite all those efforts, even Microsoft did not implement JS on .NET in IE. This despite Microsoft more than anyone having the capability and moreso the motivation ("everything on .NET"). Microsoft gave up and implemented a new JS engine in native code, and it made that new native JS VM a peer of .NET in Windows 8.

Even given the above, implementing a custom optimized JavaScript VM -- even if it was only available in JS-only case -- would not be a failure scenario.

Re:Why don't they implement Python and Ruby on the web brows... by azakai on Friday December 16, 2011 @04:52PM (#3362493)
> I'd argue the opposite regarding tremendous efforts and motivation; dynamic languages were an after-thought for both the JVM and .NET, and on the JVM side you've only seen any attempts to improve performance recently, with invokedynamic for Java 7.

> The investments here occurred long after the VMs were developed.

That's a valid point. It is possible that some entirely new kind of VM could work, that was designed from the ground up for both static and dynamic languages. But I don't think we have any good idea of such a thing!

Until we do know how to do this, replacing the JS VMs in browsers would slow everything currently running. And adding another VM alongside it would decrease speed in other ways (see for example the papers that the Apple dev mentions in the WebKit discussion for why Apple opposes adding the Dart VM into WebKit).

Re:Why don't they implement Python and Ruby on the web brows... by nupark2 on Friday December 16, 2011 @05:11PM (#3362565)
I think your points are valid as well.

I'm not ready to take it as a given that we can't build a general purpose VM capable of running JS at or very near current speeds, but it's also not a solved problem.

Re:Why don't they implement Python and Ruby on the web brows... by azakai on Friday December 16, 2011 @05:47PM (#3362682)
I agree, I don't think it's impossible. But, we don't know how yet.
Re:Why don't they implement Python and Ruby on the web brows... by tikhonj on Friday December 16, 2011 @02:40PM (#3361969)
It's not the lisp extremists that want this, it's the Python and Ruby ones. Lisp people already have plenty of options: I can think of ParenScript and ClojureScript off the top of my head. (And I'm not even (much of) a Lisp weenie. :)

(parenscript http://common-lisp.net/project/parenscript/)

(clojurescript https://github.com/clojure/clojurescript)

Re:Why don't they implement Python and Ruby on the web brows... by rbxbx on Friday December 16, 2011 @06:49PM (#3362846)
>If you really don't have the skill required to use Javascript...

So it's a lack of skill that makes JavaScript a poor choice for largescale application development?

No.

Developers like this are a large part of the reason we can't have nice things.