JavaScript is widely used these days. But there are still many people who dislike it, which is why Dart and – to a lesser degree – CoffeeScript have passionate fans. Recently, Crockford, who has done much to establish JavaScript as a credible general-purpose programming language, called it “tragically important”. In this blog post, I argue that we should see JavaScript’s glass (cup?) as half full and not as half empty.
The “Zen of Python” is a mini style guide for Python code that is also interesting if you don’t program Python. Its abstract reads:
Long time Pythoneer Tim Peters succinctly channels the BDFL's [Benevolent Dictator For Life, a nickname of Python creator Guido van Rossum] guiding principles for Python's design into 20 aphorisms, only 19 of which have been written down.
This blog post explains how to use Node.js to reload a tab in Safari whenever a file changes. Alas, this solution only works on a Mac, because it relies on AppleScript to remotely control Safari. You can download it as project JSReload on GitHub.
Are you looking for an alternative to Facebook and Twitter? Do you think they should work more like email, with multiple servers, multiple apps, and the ability to move and back up your content? Then distributed social networks may interest you.
Several tweets mentioned that in order to display an element in Chrome’s JavaScript console, you only have to type its ID.
@johnjbarton pointed out that that is because all element IDs are global variables. This blog post explains a few more details.
Underscore.js is a useful complement to JavaScript’s sparse standard library.
This blog post takes a closer look at its extend function. Along the way, it will give a detailed explanation of how to best copy properties in JavaScript.
This post requires basic knowledge of JavaScript inheritance and prototype chains (which you can brush up on at [1]), but should be mostly self-explanatory.
Did you know that defining a property is not the same as assigning to it? This blog post explains the difference and its consequences. It has been triggered by an email from Allen Wirfs-Brock on the es-discuss mailing list.
TC39 (Technical Committee 39) works on the upcoming ECMAScript.next [1] standard. They have several meetings per year and in July, there was another one. This blog post summarizes the most important decisions. It is based on the following minutes by Rick Waldron: