Yep. I'm already sour against the IRS from just doing some tax calculations, saw the article title, and didn't even read the article before commenting! Edited my comment.
+1 -- I use Stout all the time. I don't have to rely on anyone's uptime except AWS's. Stout's just a "shortcut" for using AWS infrastructure that I have full control of.
With Surge, I'd have to trust some startup's build tool not to fail at a vital time.
A good micro-module removes complexity. It has one simple purpose, is tested, and you can read the code yourself in less than 30 seconds to know what's happening.
Take left-pad, for example. Super simple function, 1 minute to write, right? Yes.
The fact of the matter is: every line of code I write myself is a commitment: more to keep in mind, more to test, more to worry about.
If I can read left-pad's code in 30 seconds, know it's more likely to handle edge cases, and not have to write it myself, I'm happy.
The fault in this left-pad drama is not "people using micro-modules". The fault is in npm itself: all of this drama happened only because npm is mutable. We should focus on fixing that.
I'm not sure if you're being sarcastic here. But again, there was no passive aggressiveness in my previous comment. I meant what I said, and nothing more: He's assuming things about someone he doesn't know. That's something to be careful with.
Now linting full codebase on precommit and it’s faster than just linting staged files with prettier!