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 where "string
Steve is concerned [http://words.steveklabnik.com/rust-is-more-than-safety] that an overfocus on safety might sell Rust short. At its least compelling, safety turns into a PSA for you to "eat your vegetables." And he makes a good point that for people who have only worked with safe languages, it's a
People have been talking about a post about package management dependency resolution by Russ Cox that opens "Dependency hell is NP-complete [https://research.swtch.com/version-sat]. But maybe we can climb out." It does a pretty good formal analysis of the problem of traditional dependency resolution (and its equivalence to
Programming language experts like to claim that syntax doesn't matter, that semantics is all that counts. Don't believe them! They're overrotating on a common, pre-rigorous [https://terrytao.wordpress.com/career-advice/there%E2%80%99s-more-to-mathematics-than-rigour-and-proofs/] misunderstanding of language design as superficially aesthetic. The study of semantics does provide deep insights into
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
An old example:
Me: I really wish it was possible to get native-like acceleration when scrolling
on mobile devices.
Them: You can already do that with touch events!
More and more, I find myself saying "I bet that almost works."
What I mean is that while the API in question looks like it'll do what I need,
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