Hot take: tools with built-in support for Babel or TypeScript are bad for the ecosystem. They stifle competition, and make it significantly harder for a new compiler to get adoption. It also harms Babel/TS by having another tool locked to their major making it harder to iterate.
-
Show this thread
-
Replying to @sebmck
I sure as heck don't disagree, but does this apply to e.g. create-react-app as well? Realistically, most people don't want to fiddle with the toolchain, especially if what they're trying to achieve has already been done, making repeating that task a total distraction.
1 reply 0 retweets 3 likes -
Replying to @tmdpw
Deleted my original reply because it was confusing. If the reason for using a particular compiler is about having sensible defaults or to abstract things away then it seems fine. The breaker though is when config is exposed since then it becomes bound to that implementation.
2 replies 0 retweets 1 like -
That’s the trade-off. What do we think the ecosystem lacks the most? Good competition or sensible defaults? I would say there’s a huge competition in JS ecosystem and very little sensible defaults (if you compare it with other ecosystems)
2 replies 0 retweets 3 likes
Both. I think current tools are inadequate and lack good configuration.
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.
he/him 