[tacticalogic]

OO isnt programming. It is hoping that the shoulders of the giants you stand upon don’t shrug. I personally hate OO. So much ugly overhead. The friggin NSA could hide backdoors in any part you did not personally develop. OO is a very ugly fat girl and you are at the bar at closing time. Be prepared to gnaw off an arm in the morning.

Well then, don't bother with it. Limiting your skill set is always a good career move.

[LesbianThespianGymnasticMidget]

Hey now, I code for food. Just cause I think some system is crap doesn’t mean I am not the best at it. Admit the overhead in CPU cycles and memory are huge. It is lots easier to code though when other people did the actual thinking. I guess it is a trade off. Thought vs speed and efficiency, I prefer the programmer be good and his or her code be efficient and quick. No matter how smart or good the completely OO coder, their stuff runs slower than non OO stuff.

OO is good for large projects. Allows compartmentalizing thought and responsibilities, but given OS400 was written by a three or four man team, I mean big stuff.