meta VS loader

> You write this as if that mattered... Should he only works on stuff that gets more download?

It was a statement of fact. You appear to be drawing conclusions that were never hinted at nor implied. It's tiresome.

> It's normal to be sad to have lost someone that was working on something you needed, but anything else is just entitlement.

How and why are you applying entitlement and emotion to a documented statement of fact? Do you need to see links such as [1] to view that as fact? It's one of a myriad. Take your asinine analysis and commentary elsewhere, please.

[1] https://github.com/sindresorhus/meta/discussions/15

ESM is the biggest waste of time in the JS ecosystem. People are trying to move thing to ESM before it's even in a stable enough state. Mixing ESM and commonjs is a PITA. I've been a JS-only dev since 2013, and I've had enough of ESM ideologues.

See https://github.com/sindresorhus/meta/discussions/15 for just ONE example of this mess.

I don't know why it's become this ideological war where people are 'testing the waters' on production-used libraries. It's not the approach I would have taken.

Also here's some reading for you by people that are saying the same thing I am: - The dude that wrote half of npm: https://github.com/sindresorhus/meta/discussions/7 - The guy who wrote "JavaScript the Good Parts": https://www.youtube.com/watch?v=PSGEjv3Tqo0&feature=youtu.be&t=9m21s

Your first point is absolutely spot-on but I am curious as to how much treeshaking was on the minds of masses at the time. The tooling of that era didn't really have any good support for tree shaking even for non-AMD includes and it was quite experimental tech (as in, I don't think it was a decision making factor for the majority of the tools on the scene).

The second point actually isn't strictly valid. I've written my own "all-in-one" async custom loader [0] that can require() CommonJS/AMD includes or regular "add a script tag" includes w/out any exports, all asynchronously, with asynchronous dependency trees for each async dependency in turn. You can define in the HTML source code a "source map" that maps each dependency name to a specific URL, so that you don't need knowledge of the filesystem tree to load dependencies.

Ideally, this source map can be generated via the tooling you use to compile the code (e.g. `tsc` is aware of the path to each dependency) but I haven't written my own tool to generate the require path to url map.

[0]: https://github.com/mqudsi/loader