SebastianVerified account

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.

Nothing we built into the JS ecosystem is new. We're reinventing and porting tools that worked on other platforms and languages for years. You'd be hard pressed to point to a true innovation in the JS devtools ecosystem

This is a bit harsh but quite close to the truth. And we don't have a unified tool for any other language out there that does package management, compiling and linking in a single tool.

Yes we do. Rust/Cargo.

On that note, yes I do think having Metro and Yarn more tightly integrated with a zero config JS build system for both apps and library distribution could be a net positive for the community.