Linked by Thom Holwerda on Fri 8th Jan 2010 23:09 UTC, submitted by google_ninja
Permalink for comment 403373
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2006-12-27
Right! OOP was criticized for being BIG and SLOW.
Not really. It can be just the opposite and that was one of the reasons to be designed as it was.
If you use OOP planned as different libraries to be used in different situations... (just like using one set of routines for a CPU and another to a different CPU)... then you have several libraries available but just use what you need at that moment. Very low RAM consumption... and code as efficient as you wrote it.
The organization is very Tree-like. But not used as much as it should. People do not take the problem into account because it is argued that the problem is the code, not organization. The user should get more memory and a faster CPU so the team does not ALSO has to deal with organization.
However:
If such effort was made... we wouldn't have so many dependency problems... and code would be faster.
If such effort was made... the team would not have to deal later with a mess in inter-library connections.
But it would also eventually break at another point... it always does.
The point is: OOP can be faster and smaller. People just do not care after the code shows to work.
C. Moore (creator of the FORTH language) showed how-to in the philosophy of (and tips on using) FORTH. I still believe that it is the best programming language training available. But that is a personal view.