In general I agree that almost no tech has a peak popularity greater than 10 years. However, I don't see "de facto standard" as a barrier.
1: I want to be clear: The latest libraries I've written use Webpack to bundle tests. @tomdale has been using Webpack on a Glimmer project.
-
-
2: I've also used Rollup (for glimmer itself and new glimmer projects by default) and Broccoli (for ember apps and some libs).
-
3: This is (emphatically) not me grousing because something I don't use is "winning". I (and
@tomdale) would like nothing more than to ... -
4: feel really great about webpack for our code-splitting use cases. But what I want more is for the ecosystem to have a great solution.
-
5: My original tweets weren't targeted at webpack but it seems ppl want to talk about it (
#NerdSniped). -
6: There's generally not enough willingness to take critiques seriously, especially around the most popular projects. Almost every time ...
-
7: I critique something in the JS space the dominant opinion is that I'm just whining because I'm "losing" (whatever that means).
-
8: I used to criticize node, and I adopted it once it was reliable enough (in like 2010).
-
9: I used to criticize npm (I collaborated on yarn!) but lately I've been using npm5 since my biggest issues are alleviated.
-
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 ...
-
12: enamored by the idea of a "defacto standard" ("Like jQuery™") that discussion about drawbacks and limitations is discouraged.
-
13: While I'm on this topic, I want to mega-hat-tip
@sebmarkbage for engaging like a boss on limitations of React. -
14: I still like Glimmer's architecture better, but I'm beyond thrilled that the React team worked on Prepack and Fiber.
-
15: In the Ember community, we spend a whole lot of time thinking (both privately and publicly) about what we could be doing better.
-
16: I would really encourage more communities to engage in a public dialogue about deficiencies and improvements.
-
17: If nothing else, it will help users avoid the whiplash of "everything is awesome and we have the best solution ever" followed ...
-
18: a week later by a number of breaking changes because "everyone knew that solution was terrible."
-
19: In closing, I think "defacto standard" makes these head-in-the-sand tendencies worse, and I think ...
-
20/20: we should be working much harder to identify and publicly discuss deficiencies in our approaches.
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.