Haha! True that. Light years is definitely a measure for distance 😂 A quite long distance though…

So. How small is a too small module? What is exactly a module? Why even is modules a good thing? As you point out modularizing code even makes the codebase larger. Actually I think those questions are quite legitimate to ask. And honestly those questions moves things forward. That’s kind of my point in the article, we — as a community — waste our time when we are criticizing, instead we should spend our time coming up with better solutions and help fix it.

Modern front-end is not perfect, but the pace and engagement in the community are quite awesome. Speaking of that, Facebooks new package manager seems quite interesting btw 🙂 And for practical reasons I know there is quite common for larger dev teams to have a local dev server with the most common NPM modules.

Why I think the idea how a huge base library might not be good? Who should be responsible for it? Who should decide what it contains? I don’t see any problem by trying to solving problems 128797 times, the change it is getting better the 128780th is quite huge. That’s kind of the power in the community, never stop trying to improve. The web moves fast, and so are our tools.

Maintaining NodeJS in the future. I don’t quite see how that differ from maintaining other kind of applications. Hopefully they aren’t as large as the prehistoric monolith applications, but divided into micro-services, separate front-ends, smaller modules… 😉