Linked by Thom Holwerda on Fri 8th Jan 2010 23:09 UTC, submitted by google_ninja
Windows As inevitable as the tides rolling in: every time a new Windows version is released, someone with too much time on his hands tries to install it on extremely outdated hardware. Sure, it won't be usable by any standard whatsoever, but it's still a fun thing to do. Of course, Windows 7 couldn't lag behind.
Thread beginning with comment 403373
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Why hardware... is outdated?
by dulac on Sun 10th Jan 2010 01:17 UTC in reply to "RE: Why hardware... is outdated?"
dulac
Member since:
2006-12-27

Object oriented programming, which is what I assumed you meant by object coding, had more to do with development speed and robustness than high performance code.


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.

Reply Parent Score: 1

kaiwai Member since:
2005-07-06

"Object oriented programming, which is what I assumed you meant by object coding, had more to do with development speed and robustness than high performance code.


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.
"

I think the criticisms of OOP come from bad experiences with Java; so unfortunately OOP become synonymous with Java and all the crappy slowness that comes with the territory. With that being said, I'm a Luddite and I stick to my old procedural languages. I'm sure OOP is wonderful but I've never been able to get my head around OOP but that is probably due to exposure to Java via an O'Reilly book more than anything else.

Reply Parent Score: 2

deathshadow Member since:
2005-07-12

That's why you should look at object pascal - in Wirth family languages where pointers are already typed and you have 'record' instead of 'struct' objects make a HELL of a lot more sense.

In most of your AT&T Syntax languages (C++, Java, PHP) objects are such a convoluted mess they feel like they were bolted on last minute - not like they are an actual useful part of the language. In Modula and Object Pascal (like Free Pascal or Delphi) it's an extension of the 'record' type and the handling/inheritance is a hell of a lot clearer.

Even if you are going to use them in other languages, I suggest taking the time to learn them in Delphi and/or Free Pascal first so you can figure out how they are supposed to work, BEFORE you waste time trying to use them in environments that have half-assed implementations.

Especially when said implementations are in languages that are already needlessly cryptic and likely all little more than a cruel joke.

Edited 2010-01-11 00:43 UTC

Reply Parent Score: 3