Thanks for the links!
- does something rather novel
- does something that, to the sufficiently desperate or inept developer, might seem like a half-decent idea or a cunning shortcut
- does something that is just asking for trouble and that nobody in their right mind should do without expecting terrible, terrible things to happen
- does something that is just asking for trouble and that nobody in their right mind should do without expecting terrible, terrible things to happen
In reality, even if this is satire (which I believe it is) I'm sure if enough people will know about it, at least one of them will use it seriously.
If you want to go the other way, try
window.onerror = window.close;Putting aside the fact that this project is probably satire, how is this a "these days" thing? Code in the bad old days was just as littered with ON ERROR RESUME NEXT, if (err) {/＊this cant happen＊/ return;} and catch {/＊do something here＊/}
As for the "these days" comment, why is it that people are repeatedly convinced that human habits have changed that drastically in their lifetimes? This "change" is the result of perspective, no more, no less.
OTOH, I would actually say that things have improved of late.
Just in the last couple of decades we've seen what I think are the first serious approaches to error handling. Think about things like the Abrahams Guarantees, or all those fun category-theoretic analyses that the functional folks keep generating.
And then the stakes have gotten higher. Thirty years ago, if a user gave a program messed-up data, then we could shake our heads and say, "Stupid user." Today, large companies put mission-critical functionality on the web, opening it up to people with both the time and the inclination to generate messed-up data in an attempt to bring the system down.
The result of all this is that, just in the last one or two decades, we've finally seen a significant number of large software packages that actually work.
And that, IMHO, is not a trivial development.
Python has an API for inspecting the AST.
I want a fuckit.hs
Sometimes the effort involved in "properly" initializing someone's module far outweighs whatever potential benefit you get out of the module - this seems to subvert that quite nicely.