Quote:
|
Originally Posted by JetLinus
I bet noone asks me, BUT:
IMO oo is for mega-projects. Like windows for example. When lots of people work on one huge project, and it needs to be coordinated and structured in some way.
If you're programming on your own, ah well, don't worry too much. If your variable- and function-naming and -handling etc is consistent enough, you'll probably do very fine with good old spaghetti code (in a good way). Well, probably "procedural programming" is the word I mean.
But as soon as other people have to use your code.... Well, oo HAS it's right of existance.
But I seriously doubt, that most hobby / amateur programmers ever used inheritance in a really sensible / useful way.
|
The absolute best coding environment I have ever experienced was in an LPC mud, and all the code was OO. But I guess that counts as a "mega-project" even if it is a hobby/amateur thing.
But please note; if you are going to put code away for some time, and come back to it later, you count as a different person.