Any one out there reading my blog know if writing Java in proper OOP causes faster execution? I have a friend that basically counts instruction sets of every line of code he writes, and avoids instantiating objects because "it costs to much". Now, this doesn't mean that his code is all in one huge object :) but it does make some of his design decisions go in... weird directions.
He stated today that he could take any OOP system, and make it non-OOP and it would be faster. He did agree that when you go to update said non-OOP software that it would be a nightmare. Finally, his primary argument is that OOP causes developers to use good design which in turn leads to faster code. So I am confused as to why he wouldn't want to use good design and give up counting instructions.
My question is, does the JRE have an optimizer that understands OOP and somehow makes more OOP-ified code run faster?
Posted by carl at April 25, 2003 12:34 AM
Comments