There is two games where some serious wounds drive you to finish them on one leg, your knees or with one eye (Only half of the screen remains visible... Very funny) :
- Savage
- Robinson requiem
Savage was one of the first "real 3D world" game in the early 90's, i finish it on a 8 bit CPC... A hard but very good game, that worth the endeavor.
I can't agree. Any software MUST use the _less_ memory/ressources possible for his functionning, and SHOULD use the _most_ the available memory / ressources for caching purpose (Except the applications that are memory / ressources stress tests, indeed...).
The first goal is to function, the second is to use the lowest possible level of ressources for that while maintaining required performance level.
(with the help of an electronic translator, hope this is readable)
I'm just fully agree with you.
they are probably working at the wrong level of abstraction
Abstraction is a smart way of programming, but coding that way must not preclude a developer to take into account the management of the "mechanics", such as resource management (memory, disk space, etc..). The next generation of developers (<30 years) studied with Java, Python and other high level languages that discharge them of many tedious tasks. The downside to this approach is that it "disconnects" the developer of the system's internal functionning, which drives developers to lose the habit, among other, of monitoring the consumption of resources.
The object of all software development is mainly to manage resources to achieve a goal. Low skills in terms of mutlithread programming and design for today's developers in an era of multi-core processor aptly illustrates this fact.
Slashdot Mirror
Savage was one of the first "real 3D world" game in the early 90's, i finish it on a 8 bit CPC... A hard but very good game, that worth the endeavor.
the ideal should not be the opposite extreme.
I can't agree. Any software MUST use the _less_ memory /ressources possible for his functionning, and SHOULD use the _most_ the available memory / ressources for caching purpose (Except the applications that are memory / ressources stress tests, indeed...).
The first goal is to function, the second is to use the lowest possible level of ressources for that while maintaining required performance level.
Proxy side effect, i did'nt want to post this one anonymously...
(with the help of an electronic translator, hope this is readable)
I'm just fully agree with you.
they are probably working at the wrong level of abstraction
Abstraction is a smart way of programming, but coding that way must not preclude a developer to take into account the management of the "mechanics", such as resource management (memory, disk space, etc..). The next generation of developers (<30 years) studied with Java, Python and other high level languages that discharge them of many tedious tasks. The downside to this approach is that it "disconnects" the developer of the system's internal functionning, which drives developers to lose the habit, among other, of monitoring the consumption of resources.
The object of all software development is mainly to manage resources to achieve a goal. Low skills in terms of mutlithread programming and design for today's developers in an era of multi-core processor aptly illustrates this fact.