luketheobscure

6 ms·

31.
by luketheobscure 9y ago
This article is missing one important thing: CoffeeScript now supports native import and export statements, but decaffeinate doesn't. I recently migrated several large codebases and had to escape all the import and export statements (w
32.
by luketheobscure 9y ago
Almost all of his arguments are also true for Ember.js, with the notable exception of compatibility with "web components" (but there's Glimmer for that).
33.
by luketheobscure 10y ago
I've been working full time on Ember stuff for a long time now, and I can not imagine a single reason to ever fork Ember. I've used different programming languages (CoffeeScript, don't make fun), templating languages (Emblem.
34.
by luketheobscure 10y ago
I don't think there's any "in-room elephants": - Glimmer 2: Shipped - Ember/CLI 3.x: Haven't heard anything, but there's not really any features that have been pushed to those versions that I know of. Glim
35.
by luketheobscure 10y ago
I can't imagine where that 20 minutes number came from. Maybe a fresh `git clone && npm install && bower install && ember start`... But even then that seems very high (and somewhat irrelevant since subsequent bu
36.
by luketheobscure 10y ago
His summary doesn't at all reflect what was in the phone call that he posted. He says that Apple insisted he admit wrongdoing, but the representative from Apple was very clear about the three points he wanted expressed (his account was
37.
by luketheobscure 11y ago
Interesting how I felt total empathy for the author up until about 2/3 of the way through, when I started to wonder if he was, perhaps, just a jerk. Probably somewhere around when he started comparing his publisher to the Nazis.
38.
by luketheobscure 11y ago
Ember 2.0 came out after 1.13, so there's 4 versions between 1.9 and 2.0. 1.13 added a bunch of deprecation warnings to all the features they were going to strip out, and 2.0 only removed code previously marked as deprecated. So maybe
39.
by luketheobscure 11y ago
I think Ember is ahead of the curve on this one. Ember 2.0 introduced no new features, and instead only focused on stripping out deprecations, dead code, or platform specific stuff for browsers they don't support any more. (Disclaimer:
40.
by luketheobscure 12y ago
Which happens when you run Instruments. I had a project with this exact setup about a year ago... The amount of time lost resolving conflicts wasn't worth it.
41.
by luketheobscure 12y ago
Should be titled "How to create conflicts with every commit".