10: I used to criticize Babel (back in the days when we maintained our own module transpiler) but we adopted it and ran with it.
-
-
11: The assumption in the JS ecosystem that criticism is "whining because you're losing" is what I'm talking about. People are so ...
1 reply 0 retweets 1 like -
12: enamored by the idea of a "defacto standard" ("Like jQuery™") that discussion about drawbacks and limitations is discouraged.
1 reply 0 retweets 1 like -
13: While I'm on this topic, I want to mega-hat-tip
@sebmarkbage for engaging like a boss on limitations of React.1 reply 0 retweets 1 like -
14: I still like Glimmer's architecture better, but I'm beyond thrilled that the React team worked on Prepack and Fiber.
1 reply 0 retweets 2 likes -
15: In the Ember community, we spend a whole lot of time thinking (both privately and publicly) about what we could be doing better.
1 reply 0 retweets 1 like -
16: I would really encourage more communities to engage in a public dialogue about deficiencies and improvements.
1 reply 0 retweets 1 like -
17: If nothing else, it will help users avoid the whiplash of "everything is awesome and we have the best solution ever" followed ...
1 reply 0 retweets 2 likes -
18: a week later by a number of breaking changes because "everyone knew that solution was terrible."
2 replies 0 retweets 1 like -
19: In closing, I think "defacto standard" makes these head-in-the-sand tendencies worse, and I think ...
1 reply 0 retweets 1 like
20/20: we should be working much harder to identify and publicly discuss deficiencies in our approaches.
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.