Me to @slightlylate "Slow down you'll make mistakes going so fast" @slightlylate to me: "We'll fix them later." Turns out we're both right.
1
3
.@mollydotcom : I argue for going lower-level and being evidence based about community use; not quite the same as fast/slow
2
.@mollydotcom: the features I design have clear community use/pain: Web Components, Service Workers, Promises, Classes, Progressive Apps...
1
1
4
Unquestionably difficult pain point @slightlylate - remember also that conversation we had was ca. 2009. We're probably a bit wiser now :-)
1
@mollydotcom : I'm sure not = ) But in '09 was doing Chrome Frame and was very frustrated by lack of progress; ¯\_(ツ)_/¯
1
1
Replying to @slightlylate
Chrome Frame was exactly the topic @slightlylate Oh boy do I remember! Do you think we're in a better or worse place overall now?

Aug 3, 2015 · 4:21 PM UTC

1
Replying to @mholzschlag
@mollydotcom : hard to tell. Competition has a muted effect now (see iOS) which lowers progress rate, but distribution/update mostly fixed
1