News for hackers. Stuff that matters.
Re:Ask HN: Why did JavaScript win the browser? by malisper on Saturday August 30, 2014 @03:24PM (#8247333)
According to Wikipedia[0], Brendan Eich was originally supposed to put Scheme in the Netscape web browser. Instead he decided to create Javascript and used that instead.

[0] http://en.wikipedia.org/wiki/Brendan_Eich#Netscape_and_JavaS...

Re:Ask HN: Why did JavaScript win the browser? by yellow_and_gray on Saturday August 30, 2014 @05:03PM (#8247593)
Thanks for this link. It points to http://www.computer.org/csdl/mags/co/2012/02/mco2012020007.p...

"When Netscape hired Brendan Eich in April 1995, he was told that he had 10 days to create and produce a working prototype of a programming language that would run in Netscape’s browser. Back then, the pace of Web innovation was furious, with Microsoft suddenly making the Internet the focus"

and

"[it] needed to be a silly little brother language."

It seems it was important to implement the language quickly rather than try and make it too good.

Re:Ask HN: Why did JavaScript win the browser? by uhsnamih on Saturday August 30, 2014 @04:24PM (#8247487)
What prevents adding other languages to the web browser even now?
Re:Ask HN: Why did JavaScript win the browser? by icebraining on Saturday August 30, 2014 @07:55PM (#8247942)
Getting people to agree on which should be added. Adding new languages is only useful if they're widely supported by browsers.

Google is trying with Dart, they already have a fork of Chromium with a VM for it[1], but it still needs to be compiled to JS to support other browsers, and to many developers that loses its appeal.

[1] https://www.dartlang.org/tools/dartium/

Re:Ask HN: Why did JavaScript win the browser? by BrendanEich on Wednesday September 03, 2014 @04:40PM (#8265342)
And they need a way to avoid cyclic leaks among Dart and JS via the DOM. That adds a tax in the form of write barrier overhead, which caused Apple to reject the WebKit patch.

https://lists.webkit.org/pipermail/webkit-dev/2011-December/...

Re:Ask HN: Why did JavaScript win the browser? by curtis17 on Thursday September 04, 2014 @09:51AM (#8268197)
The most interesting way forward re languages/runtimes looks like something Brendan mentioned here: http://javascriptjabber.com/124-jsj-the-origin-of-javascript...

> At some point, Sweet.js ties the knot and people can write hygienic macros and extend the language.... And it’s all based on a common set of primitives and that’s the important thing. You can reason about the primitives. You can compose them. They’re compositional. They compose orthogonally. That’s the goal here. JavaScript has a lot of warts in it, but if you weed those out or deprecate them you end up with stuff that is compositional. And that’s where I think we’re heading.

Re:Ask HN: Why did JavaScript win the browser? by curtis17 on Friday September 05, 2014 @10:53PM (#8277326)
Scala moving in a similar direction.

Odersky: That's going to be a more fundamental rethink of what Scala is. The main goal is to make it simpler, to review it or work out what its core is, and have a very simple core on which essentially the other features of Scala can all be based. Essentially, it's a way to modularize the language better, to base the features that we know from Scala on a very, very simple core that we can compile efficiently and reason precisely about. That's the main goals for Don Giovanni.

http://www.infoworld.com/t/java-programming/scala-founder-la...