TJ Holowaychuk, a long-time Nodist (from a Nodist colony?) who has contributed much to Node, finally…
Dear ECMA,
For years, you’ve been trying to improve the JavaScript language, but you’ve not…
Eric Elliott and Douglas Crockford tout functional programming (or FP) and prototype-based OOP as the two “pillars” of…
The following video nicely illustrates some of the many semantical and syntactical WTFs that plague…
I believe in using “the best tool for the job,” too. As you say, the best tool must be determined in the context of your particular problem. However, if you’re a wide-ranging developer who works in a variety of problem domains, whether it’s over the…
I have to say, I like you. You are very intelligent and funny and charismatic and well-spoken and passionate about programming. This article (and many of your videos) almost convinced me that JavaScript is worthy of investing my time and energy into it.
Interestingly, Alexei Boronine wrote a blog post 3 years ago called, “Why JavaScript Still Sucks” that echoes my sentiments…
I think the root of the problem with modern JavaScript and the main reason that the language still sucks lies in a certain sentiment of the JavaScript community, the sentiment that JavaScript was a…
The point of the article is that there really isn’t a scenario where JavaScript is “best.” The reason is because JavaScript is fundamentally a broken language. Sure, it has a large user community. Sure, it has a large ecosystem. Sure, there are lots of employment opportunities for JavaScript developers. But none of this alters the fact that…
This is all very interesting, but I seriously doubt that prototype-based OOP will catch on in the IT community at large. Developers everywhere show a clear preference for classical OOP. Recent new languages such as Newspeak and Dart eschew object prototypes in favour of classes; the creators of those languages, Gilad Bracha and Lars Bak respectively…
