3 ms·
Could something like this be caught by static analysis?
by simonmales 5y ago
Could something like this be caught by static analysis?
- throwanem 5y agoYes. You could write an eslint rule for it, and there are probably a few of those already.
- c0l0 5y agoCould it? Yes. Will it? Maybe. Would I count on it in all cases? No. Also, I find it preposterous to rely on a second automated system to cancel out the mistakes the first one made.
- papito 5y agoIsn't this the principle the entire Javascript/Node ecosystem based upon? Downvote away. You know who you are.
- handrous 5y agoAs someone who's done a ton of JS/TS development, for browsers and Node, I thought the principle the entire ecosystem was based on was up-to-the-minute crowdsourcing of not only a standard lib, but also 90% of your basic tools and about half of what ought to be language features. Not relying on automated systems to cancel out the mistakes of automated systems.
- papito 5y agoAs someone who spent two weeks trying to get a Typescript project working under Webpack when migrating to Vue 3, by stitching together a web of gratuitous tooling and transpilers that ultimately did not work (I went with Vite and it was all working in 2 hours)... Also, I just checked out an old Flask/Python project from 7 years ago, updated it to use Poetry dependency management, and it all still works. A JS project that is 7 months old and unmaintained would be a dumpster fire.
- handrous 5y agoOh, for the "build" tools, yeah, that's actually entirely true. It's a bunch of automation fixing bad decisions and other, bad automation. Spot on.