News for hackers. Stuff that matters.
Re:Towards a More Modular Future for JavaScript Libraries by davedx on Monday November 11, 2013 @10:14AM (#6711967)
What about closures and first class functions?

Or easy interop (JSON), object and array literals?

JavaScript has more going for it than platform ubiquity.

Re:Towards a More Modular Future for JavaScript Libraries by knome on Monday November 11, 2013 @11:11AM (#6712261)
While it certainly has good points besides platform ubiquity, if you were trying to derive an equivalent of big-O for the popularity of javascript, language level criticisms and acclamations would count as, at best, linear concerns, where platform ubiquity is an exponential concern.

Platform ubiquity is so completely important in the determination that all other concerns can be ignored entirely.

Given a choice of supporting half of systems in javascript, and all systems in brainfuck, people would begin writing brainfuck-targeting compilers immediately.

Re:Towards a More Modular Future for JavaScript Libraries by taybin on Monday November 11, 2013 @01:07PM (#6712950)
All the cool programmers use CoffeeFuck.
Re:Towards a More Modular Future for JavaScript Libraries by pekk on Monday November 11, 2013 @04:46PM (#6714288)
Many languages have these things.

The problem is this spurious inference drawn from package count to language superiority. In reality what's popular is targeting browsers, and there simply aren't any other languages with first-class support by browsers no matter how much we want them. This isn't a matter of Javascript being better than everything else, it's a matter of historical accident and network effects.