Yehuda Katz

The first Ember view layer was designed kind of like you'd expect: it treated the "template language" as a very specialized external DSL with a decent amount of special syntax. In addition, the implementation was very ad-hoc, which led to a number of persistent, whack-a-mole bugs (including cases

Following on from Stage 2, the next step of a JavaScript proposal is Stage 3. Stage 3 Stage 3: Browser Early Adoption — Dave Herman (@littlecalculist) July 31, 2015 Official Description: "Candidate" At this point, implementations have expressed interest in the feature. In practice, proposals move to them

People have been talking about a post about package management dependency resolution by Russ Cox that opens "Dependency hell is NP-complete. But maybe we can climb out." It does a pretty good formal analysis of the problem of traditional dependency resolution (and its equivalence to the well-known SAT

[VILLAGERS] Who needs a new song? This old one's all we need [CHIEF TUI] This tradition is our mission And Moana there's So much to do -- Moana, Where You Are I just got back from the Ember Face to Face this weekend and I was reminded of a core

A few days ago, Hacker News started a self-imposed "political detox week." The idea was "no politics on Hacker News." I'll cite the argument in full: Like everyone else, HN has been on a political binge lately. As an experiment, we're going to try something new

Following on from Stages 0 and 1, the next step of a JavaScript proposal is Stage 2. Stage 2 Stage 2: Userland Early Adoption — Dave Herman (@littlecalculist) July 31, 2015 Official Description: "Draft" In my experience, this is where the real action for a feature lives. This

The other day, there was a post floating around called Why Angular 2 is Terrible. Actually, saying it was "floating around" is too weak: I saw it everywhere on Twitter, and searches for Angular on Twitter were dominated by this one post for a decent amount of time.

This week, I asked on Twitter what TC39-related topics, people wanted me to talk about on this blog. Julia Evans (@b0rk) threw a bunch of questions at me, and I'll try to answer them one at a time. @wycats who is in the meeting? do you have to implement the

Recently, I've noticed a pattern. When I present a problem that I'm having with a platform, I am often told "you can already do that with <some API that wasn't intended for this>." An old example: Me: I really wish it was possible to get native-like

One of my favorite articles about working in a highly technical field is Paul Krugman's How I Work, which he wrote while working as a professor at MIT. A decent chunk of the article is technically connected to his economics work, but his "Rules for Research" are generally

This week's meeting has a few different Promise-related spec changes. Promise.try: async function as a Library One of the goals of Promise APIs is that exceptions that happen while processing the request become Promise rejections, rather than bubbling up to the top level (e.g. window.onerror). This is

On the first day of TC39 (hosted by Facebook), we covered: the final features we hope make it into ES2017, improvements to regular expressions and promises, a grab-bag of tweaks to modules, and assorted other topics. ES2017 Last Call We started the day by looking at features that hadn't yet