All true points, many of them are what would considered poor programming techniques for the last 10 years. In the days when I started programming and all you had was a tiny amount of RAM you traded off error catching and data types against space, so you might use a short integer with a limited number of values to reduce memory size, and then not error check the stored answer. But with the advent of huge amounts of RAM ( and all the other windoze bloatware) this type of programming tends only to be used on embedded systems and is generally regarded as poor technique outside of this. I can't think of the number of times I've heard discussions on this, especially at software process group events.

(my first professional programming was in z80 machine code, hand assembled, I had 4k of ram alloted to do some sprite animation on the amstrad cpc464!) those were the days :)

Personally I think windoze could do with some thinning out and some old school care and attention, but we all tend to use auto generated code and hand assembly is a rare thing!

----------

Toolset: Blender, GIMP, Indigo Render, LuxRender, TopMod, Knotplot, Ivy Gen, Plant Studio.