I think this aligns with the web manifesto and removes the painstaking time to argue should or shouldn't.
-
-
a situation like this occurs, and a solution can not be created beyond irreducible complex. or time/cost, yield 2 threshold
1 reply 0 retweets 0 likes -
Replying to @TheLarkInn @mixonic
one approach that can work nicely is bringing new semantics in with new, more ergonomic functionality. 1/
1 reply 0 retweets 1 like -
ES6 modules for example. In DOM, renaming querySelectorAll to find could bring in better semantics, fetch did, 2/
1 reply 0 retweets 1 like -
addEventListener -> on could add better event delegation baked in, passive listeners, fix event object. 3/3
1 reply 0 retweets 1 like -
yeah that has tradeoffs as well such as no guarantee users will adopt or update. 1/
1 reply 0 retweets 0 likes -
I actually really like that approach and we use it w/
#webpack, I feel we should be using both strategies though 2/2 replies 0 retweets 0 likes -
if you add a new feature or API, we should gracefully deprecate right at the least.
1 reply 0 retweets 0 likes -
Replying to @TheLarkInn @mixonic
I think the web shld learn how to deprecate more explicitly yes, but deprecation need not imply a timeline for removal
1 reply 0 retweets 1 like -
yeah who are we championing? Users? Web itself? Developers who write for it? To me this answer helps decide aforementioned
1 reply 0 retweets 0 likes
ultimately users, but a platform is nothing without developers. Instability damages ecosystem.
-
-
yeah I don't disagree with that one bit. I keep mentally trying to reason this arg but the data/research for this outweighs
1 reply 0 retweets 0 likes -
to me. I keep seeing 95%ile and saying holy shit let's do it. That's a huge impact.
0 replies 0 retweets 0 likes
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.