The Two Pillars of JavaScript: Part 1: How to Escape the 7th Circle of Hell

Re:The Two Pillars of JavaScript: Part 1: How to Escape the ... by throwawayaway on Saturday December 13, 2014 @06:55AM (#8744989)

it's depressingly good at deployment though isn't it. there's nothing easier to "port". it's the write once run anywhere that's been promised so many times. i just don't feel like writing anything in it!

i don't think that this is a great article because there's a lot of bloat around the content to wade through and filter.

[ Parent | on HN ]

Re:The Two Pillars of JavaScript: Part 1: How to Escape the ... by jared314 on Saturday December 13, 2014 @10:54AM (#8745408)

> it's the write once run anywhere that's been promised so many times.

It has yet to even obtain Java-level "write once, debug everywhere". Most of the people talking about "isomorphic JS" and "JS is everywhere" use, and expect, a single javascript VM implementation (V8).

[ Parent | on HN ]

Re:The Two Pillars of JavaScript: Part 1: How to Escape the ... by throwawayaway on Saturday December 13, 2014 @11:53AM (#8745559)

i was under the impression that jQuery had taken care of that, perhaps i was mistaken. certainly a url is quicker to deploy than a jar.

with the exception of jQuery: i appreciate your point, even within the same browser, different js engine versions have wildly different behaviour.

[ Parent | on HN ]