They tried to cover this up. In designing ECMAScript 2015 (a.k.a. ES6, a.k.a. ES2015), the authors identified a number of undesirable side effects of their work. “Why worry?” they asked. “People will be so smitten with arrow functions and block-scope bindings that they won’t care about a few measly backwards-breaking changes.” Well I care, and […]

Tagged:

CC BY-SA

We build a lot of software at Bocoup. Like other types of builders, we tend to grow attached to the particular sets of tools and scripts we use in our work. We don’t play favorites: my colleagues support Grunt, contribute to Gulp, and maintain stand-alone tools such as JSHint. It’s easy to take familiarity with […]

Tagged:

There is a notion in the software industry that teams are either “doing Scrum” or not. That is true in some cases, but the majority of teams are using a hybrid of methodologies based on their experiences and situation. Some of this apparent isolation is linguistic: Scrum has its own terminology for some notions that […]

Tagged:

August 14, 2015. Mark your calendars. That’s my next birthday. Another important date is June 18, 2015–it’s when the ECMA General Assembly will vote on and approve the 6th edition of Ecma-262 and usher in the next era of JavaScript. On that day, all those new language features we’ve been coveting/dreading will officially enter our […]

Tagged:

CC BY-SA

Every time I contribute to JSHint, I learn a little more about JavaScript. My most recent fantastical knowledge adventure led me to the behavior of the name attribute of function objects. JSHint has an interesting but lesser-known feature: code analysis reports. When used programatically, JSHint will return an object with some data about the code […]

Tagged:

CC BY-SA

The RICG’s work is starting to wind down, but we’re just getting started at the same time. We’re a weird sort of web standards organization. We’re nebulous by design: a rallying point for anyone that wants to get involved in the kinds of new standards that most impact their daily work. We aim to prevent […]

Tagged:

Selenium is an indispensable tool for developing web applications. It allows developers to write test scripts that control real browsers and ensure their applications behave in the way that users expect. Tests like these make software development much more pleasant–developers can have much greater certainty that their application is functioning correctly even after large refactoring […]

Tagged:

CC BY-SA

Software developers never want to do hourly time tracking. I’ve seen team leads who fill out the time tracking for their whole team to spare them the trouble. I’ve seen developers agonize over what to write down: they feel like they’re estimating even when it should be a simple matter of hours. Why is it […]

Tagged:

I’ve always been a huge proponent of building sites that work everywhere — any user, any browser, any device, any context. Websites work everywhere by default, and they stay that way so long as we know how not to break them. That’s what the Open Web means to me: ensuring that entire populations just setting […]

Tagged:

Update: This proposal now has two open bugs for implementation, on V8 and SpiderMonkey. https://code.google.com/p/v8/issues/detail?id=3915 https://bugzilla.mozilla.org/show_bug.cgi?id=1135708 In this article, I’ll explore the process of adding syntax to a programming language by going through the process of designing a new JavaScript exponentiation operator, which I’ve submitted to TC39 for consideration in ES7. In many programming languages, […]

Tagged: