Javascript is no better than PHP. It is there - like Php in its time- because we have no other choice.
We're supposed to be professionals and one of our main tool is a joke.
Javascript is no better than PHP. It is there - like Php in its time- because we have no other choice.
We're supposed to be professionals and one of our main tool is a joke.
If you're going to complain about language choices, don't force everybody on Python!
I can't comment on Ruby because I have never had to use it.
What would be perfect is Scheme in the browser. And, apparently, we almost had it except marketing or management forced Eich to make it look like Java resulting in JavaScript.
Or from forking Chrome, since it's open source, and then offering your patch back to the central repo. Not sure if Firefox is open source, but could use that instead, too, if it is.
That's why I added the part about forking and contributing back. If it becomes part of the standard offering, then you don't have to worry about market share as much.
And especially if you get a portable implementation then the IE and Chrome teams might decide to adapt it in, since you've lowered the engineering cost.
> But that's besides the point. The behaviour is actually well defined
There's a good reason to not use Javascript, if there's an option to use another language in the browser, that has nothing to do with JS's quality itself: context switching. Node.js is popular due in no small part to the fact that you have to use JS anyways. The purpose of GWT, as far as I'm aware, is to make it so you have Java as an option in the client.
Chrome is a closed source browser based on the open source Chromium, and it includes some features that the open version doesn't, like embedded PDF reader or MP3 support.