3 ms·
I think ultimately this isn't the solution. The solution to insanely deep open source tech stacks is to use simpler stacks. This is really my whole problem wit
by kerkeslager 1y ago
I think ultimately this isn't the solution.
The solution to insanely deep open source tech stacks is to use simpler stacks. This is really my whole problem with the way JS is ubiquitously developed: you simply do not need 99% of the tools the JS devs are using these days. I use very simple full-stacks: so simple that I don't need a JS package manager (I do use pip/pypy, but I'm extremely guarded about what code I'll import--usually <10 packages). I do write some code that could be imported in a library sometimes, but I also barely ever do any rewriting to deal with deprecations, and my builds never break due to a package change. My builds are often reproduceable by accident.
In the short run, I'm not less productive than people who use all of npm. In the long run, I'm far more productive.
And even if that weren't the case, developer productivity at the expense of user security was a pretty bad tradeoff anyway. I really wish fewer people were doing that.