There's something to be said about the quality of programming API-kids do these days, if FuckIt.lang projects are so popular. Not to jab this project itself by any means, but hiding defects "on your way to doing that million dollar demo to investors" makes my skin crawl. How many con men are in this industry? This is damn sad. If you need a tool like this beyond your private debugging needs, you don't understand what you're doing and should step back and take the time to reason things out.
I don't think this is so much a tool as a "because I can and it's funny" project. Like Edison -> Serial "adapters" and various other hilariously, uselessly malicious things it's possible to create.
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＊/}
I can't help but facepalm when I read things like this. Even if it works, the name of the project should have given the commenter some clue that it was a joke.
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.
There are a lot more computer software jobs today than there were 30 years ago, and this caused an influx of clueless gold-rushers trying to get in. There always were bad programmers and buggy software, it's just that today there's a lot more of both (both in terms of percentage and total), simple as that.
They are popular to get cause they are funny. They are popular to make because they let you experiment around with metaprogramming magic in the language to some extent.
I plan on using this next time I have to do some quick and dirty python hacks at work.
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.
Comments
There's something to be said about the quality of programming API-kids do these days, if FuckIt.lang projects are so popular. Not to jab this project itself by any means, but hiding defects "on your way to doing that million dollar demo to investors" makes my skin crawl. How many con men are in this industry? This is damn sad. If you need a tool like this beyond your private debugging needs, you don't understand what you're doing and should step back and take the time to reason things out.
I don't think this is so much a tool as a "because I can and it's funny" project. Like Edison -> Serial "adapters" and various other hilariously, uselessly malicious things it's possible to create.
What is an Edison -> Serial "adapter". Do you have a link? Just curious.
Couldn't find one for serial, but here's one for Ethernet: http://m.imgur.com/7Mbx8yk
EDIT: There is actually a whole series:
http://www.fiftythree.org/etherkiller/
Wow that is some electronic sadism. Good for quite a few laughs when it made the rounds in my embedded systems lab today.
Thanks for the links!
Assuming this project is satire (which I hope it is), it's amazing because it:
- 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
Some people use Python as JS or PHP, why not also make it behave like that?
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
Ahh the famous halting problem and it's recursive work around for unrealistic deadlines where one simply says 'fuckit;'
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＊/}
I can't help but facepalm when I read things like this. Even if it works, the name of the project should have given the commenter some clue that it was a joke.
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.
Indeed.
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.
There are a lot more computer software jobs today than there were 30 years ago, and this caused an influx of clueless gold-rushers trying to get in. There always were bad programmers and buggy software, it's just that today there's a lot more of both (both in terms of percentage and total), simple as that.
I think the technical difficulty of what the module actually does should be a pretty clear indication that this is satire?
Opening up the AST, and wrapping it in try-catch blocks, is really not that hard in python.
Python has an API for inspecting the AST.
There's always someone who takes it seriously. (And I don't mean the parent comment.)
Are you joking? This project is blatant satire.
They are popular to get cause they are funny. They are popular to make because they let you experiment around with metaprogramming magic in the language to some extent.
I want a fuckit.hs
'spoon' is "kind of" a legitimate fuckit.hs.
I plan on using this next time I have to do some quick and dirty python hacks at work.
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.
I'm pretty sure it's supposed to be a joke.