4 ms·
I think that's an exaggerated reaction. Bugs happen all the time, is this one any different because it involved such unusual circumstance? It wasn't a security
by tekkk 7y ago
I think that's an exaggerated reaction. Bugs happen all the time, is this one any different because it involved such unusual circumstance? It wasn't a security bug, and how many users did actually freshly install Webpack on Windows-based computer on monday? Not a large subset. So it's more amusing than harmful.
Whenever things like these happen, of course you should think if the effort ripping off Webpack is better than suffering possible losses of productivity in the long run. But for majority existing projects I'd bet the projected cost of lost hours vs the cost of changing your bundler would result in net-loss.
And as an observation, I feel programmers often have a habit of lamenting loudly about other people's mistakes while not saying a word if they make an error of their own. Maybe they have a psychological need of maintaining a feeling of superiority about your own abilities, I don't know. Just something I've noticed during my years.
- hluska 7y agoJust to correct you, this bug doesn’t happen during an install, it happens when Window users run a build. Builds were badly broken 1/7 of the time because of some shady code that really shouldn’t have made it through any kind of review. And yeah, I’ve written some shitty code too, but can’t say that I’ve bricked an important tool 1/7 of the time in the name of a sketchy donation banner.