SebastianVerified account

This was part of our vision with the JS infra team @ FB with @MetroBundler, @babeljs and @yarnpkg etc, etc. @sebmck @cpojer please make it happen https://twitter.com/mcclure111/status/995678592234377216 …

I‘m not convinced that all of them merged into one tool are substantially better than separate tools that are tuned to work well together.

It’s really hard to be the best at everything at once. So it really would have to be substantially better to compensate.

It requires a substantial investment and the incentives to be aligned (why I'm not convinced open source is the place to do it). However there many historical examples: Interlisp, Smalltalk, etc. Modern examples like Go leaves a lot to be desired but still much better that JS.

I tend to prefer the Unix philosophy. A few tools that make their job well and can be compounded together to firm something better. Doesn't mean no integration, just that they should work by themselves. It seems easier this way to reevaluate parts of them periodically.

I mean, can you imagine the ecosystem if npm was such a all-in-one server? Would babel even have been possible? Webpack? Yarn?

Most these things there authors will be the first ones to tell you they wouldn't like for it to exist. They're just solving a problem they wish didn't exist.

I think they're solving a problem that nobody even understood before. And that's the problem : even now, we don't see the problems we'll have to face. Monolithic tools tend to solve the problems at hand to the detrimental of of future evolutions.