Linked by Eugenia Loli on Wed 22nd Mar 2006 18:08 UTC
Thread beginning with comment 106788
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-06-29
I do not think that programmers should generally be encouraged not to worry about the details. You should really try to be as abstract as possible but do not forget that you are not living in a perfect world - all the statements you have written will eventually translate to low level assembly (which in turn goes down to binary which we all know). So what you should really know is how much things cost - how much does it cost to allocate 100 objects, how much does it cost to do things asynchroniously, how much does it cost to call this method or the other one. If you don't really think & know about this, then I call this carelessness.
But it again boils down to "the right tool for the right job". It's not that you cannot write system software in Java or that you cannot write games object-modeled frameworks in C, it just is not the best thing to do. So I just want to say to all programmers that you should really know what you are doing and know the details. Don't use a garbage collector as an excuse for your code being slow etc.
Regards