Conversation

Notices

1. Kat Marchán 🐈 (zkat@toot.cat)'s status on Thursday, 03-Feb-2022 23:14:15 UTC Kat Marchán 🐈

   JavaScript tooling is broken, and creating more tooling that "does it better" is not going to fix what is essentially a systemic problem.

   And tbh, this is actually the NPM CLI's fault. In this essay I will...

   • Kat Marchán 🐈 (zkat@toot.cat)'s status on Thursday, 03-Feb-2022 23:14:14 UTC Kat Marchán 🐈

     in reply to

     The only way to save the JavaScript ecosystem is to do a well-resourced centralization push that ends this absolutely bullshit explosion of halfassed build tools.

   • Kat Marchán 🐈 (zkat@toot.cat)'s status on Thursday, 03-Feb-2022 23:14:15 UTC Kat Marchán 🐈

     in reply to

     here's a bold claim: The *only* way to "fix" JavaScript tooling is for the community to come together as one and build a proper build tool/transpiler/task runner/bundler/test runner *INTO NPM PROPER*.

     Anything else is going to just make the problem worse.

   • Kat Marchán 🐈 (zkat@toot.cat)'s status on Thursday, 03-Feb-2022 23:14:15 UTC Kat Marchán 🐈

     in reply to

     ooh. Preemptively changing this to people-I-follow because I know there's a lot of people with Wrong Opinions on this that are going to respond to me as if I'm not speaking the truth they don't want to hear.