m1abrams wrote:
First SC does a good bit more than those games of 30+ years ago.
Second coding for efficiency can be very expensive and many times not
worth the return. It also can lead to sacrificing maintainability
which in the case of an open source project can lead to the end of it.
I pride myself on making my code lean and mean most coders do, however
when working with deadlines I know my client wants stability over lean.
Reason, they have no issues throwing hardware at it, it is much cheaper
than my billing rate.
I have not looked into SC code, however I am willing to bet a good bit
of the memory is consumed by indexes. And no using more memory does
NOT equate to using more CPU power.
Often it's the other way around. You spend more memory to save time.
To the comment about being worried about the times ahead because of
coders saying exactly that "throw hardware at it". Well you need to
understand hardware is cheap, labor is expensive, and money runs the
business.
As we have said over and over, if you think you can do better it is
completely open code, Have at it.
"We should forget about small efficiencies, say about 97% of the time:
premature optimization is the root of all evil." (Knuth, Donald.
/Structured Programming with go to Statements/, ACM Journal *Computing
Surveys*, Vol 6, No. 4, Dec. 1974. p.268.)
Write the code and wait 'til the hardware catches up ;)
Regards,
Peter
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
