3 ms·
For me the important point was that the implementer cannot delegate the community discussion to someone else. He needs to be part of it, and waste hours of impo
by rurban 8y ago
For me the important point was that the implementer cannot delegate the community discussion to someone else. He needs to be part of it, and waste hours of important development time on bike shedding.
Or just ignore it and apologize afterwards for rendering the bike shedding useless.
- sgift 8y agoYeah, it is bike shedding to discuss dependency management, because dependency management is an "insignificant or unimportant detail" of a programming language. /s
- majewsky 8y agoYou say "/s", but for some reason, many people still hold the sincere position that dependency management is something that can just be tacked on to a language as an afterthought.
- coldtea 8y agoOf course it can. npm, composer, etc all added it to their respective languages as afterthoughts, and many years (or decades even) after the language was out.
- al2o3cr 8y agoGiven the whole mjs-vs-js situation with npm, it's more of a counterexample for adding dependency management late.
- coldtea 8y agoThat's nothing really. They have to use 2 different suffixes to denote 2 kinds of files vs modules. Meanwhile millions of people use it for 10 or so years for all kinds of deployments. If only all languages had that unimportant problems.
- rurban 8y agoIt's bike shedding when you have no actual idea about the problems and solution, but decide on something anyway. The implementor in the meantime figured it out by himself and just did it.