The state of JavaScript modules
I support innovation and people who like to code and build great things. And am happy to see JS is getting these features. I even see a downvoted comment to &quot;just use amdefine&quot;. Well that solution worked fine for me, then 5 years of amazing hop scotch between build tools and libraries happened.<p>And while some report benefits and advancement, I have to tell you, the amount of tools you have to pull in these days just get some single page interaction going... Just stop. And we need to draw a line between &quot;progress&quot; for the language and its libraries vs introducing features without discipline. The more features a language has, the harder it will be for open source and industry to develop consensus on what&#x27;s idiomatic.<p>Want to know another language feature? Being stable.<p>I swear, it&#x27;s like the language reinvents itself every year. Give me some sort of promise when you&#x27;ll leave the standard alone, <i>then</i> I&#x27;ll wait for the community to form best practices &#x2F; libraries to catch up. After the dust settles, I&#x27;ll invest time reading up on the standard.<p>Ain&#x27;t trying to jab javascript. Love the language, community is top tier, but everything these days from build tools to libraries seems like a moving target.