The most evil I ever had to deal with was COBOL, probably because I never figured out what the heck I was doing.
I just found an esoteric programming language called 'evil'. (http://esolangs.org/wiki/Evil). Every lower case letter is a command, meaning that every text file is a legal 'evil' program :).
I got this "Hello, world!" program in evil from the website above:
:eek: That is absolutely insane! Lets add it to our super evil robot. :D
All Programs are evils if programmed by those Devils.
See there's a "D" (Developers) infront of "evils".
This is going to be one sick robot...
Although I don't think it should be programmed in Evil, however it should output everything in Evil :P
And Mr. Initial Man, Spaghetti PHP is one of the ugliest forms of Spaghetti code since there are many similar functions\variables in PHP to accommodate people of various backgrounds... then add people that don't know how to use Objects yet use classes anyways (like the guy we had just fired where I work), mixed with several other schemes, it can get hideous...
... OOP was "created" to make programming easier, not more difficult. Some really great programmers see OOP as a bad trend that allows shoddy programmers to get by while preventing good programmers from creating really great code.Quote:
then add people that don't know how to use Objects yet use classes anyways
For instance, the one guy did everything procedurally, however half of his code was done as functions, the other half as functions inside of a class, the functions inside his class he'd still push all the data through parameters instead of utilizing the extremely useful and easier to maintain $this. Not to mention he used several naming conventions ta-boot. As you can imagine his code then became a vicious maze trying to figure out what exactly he was trying to do. All in all I'd end up having to rewrite most of it and trim out a lot of redundant\useless code...
Great programmers will say it all depends on the task at hand.
OOP is nice for solving complex problems. But again, the OOP wouldn't be necessary if the problem-solver was smart enough to think of the problem as a whole to begin with.
Am I saying we should avoid OOP? -- Absolutely not.
Am I saying we should use OOP when we have the chance? -- Hell no!
So, what am I saying?
OOP allows lesser minds to program effectively without having to know a damn thing about good coding. It allows folks to rely on the underlying system to just "know" the best way to do things. That's the whole idea ...
... and the whole idea is shown to be quite faulty when you start working with complex systems wherein the programmers have started with a set of classes and ignored the internal functions of those classes. The end result is code that runs significantly slower than the "procedural" counterpart code. You end up with programs that consume thousands of lines of code, when 10 or 20 easy-to-understand lines of well-thought-out code are better.
So ... when do we use object-oriented code? When the problem is beyond our tiny little brains. And, as fallible humans, that'll be quite often.
Just don't make the mistake of thinking OOP is a step up for programmers ...
EDIT: So, the language of choice for an evil genius will decidedly not force object oriented programming on our genius. He's too smart to be constrained by objects.
I'd agree with that to some extent. OOP has many great features\skill sets and when more programmers are developing on a team having core classes and a standardized naming convention help greatly keep things organized and self contained. Not to mention that it becomes quite easy to manipulate any new data or build upon as long as one develops their class properly. Which in the end run will help avoid reinventing the wheel from project to project.
As for the story I'm writing it's still not certain what language will be used. Still a toss up between Java and C, would love to go with Visual Basic (that seems very evil of a language), however want the language to be developed on FreeBSD (devil logo made that choice easy). BASH\perl still stick out as well though, however for the task at hand C seems the most practical for what they're developing (it's an extremely huge\complex system).
The BASH/Perl combo would be pretty deliciously evil ...
basic.... and i mean basic basic... the begining... why i hated it...
01 type some code
The redundancy of typing out your own line number....... drove me crazy...
Unix not so bad, linux was fun
DOS lets just not go there either....