Linked by ebasconp on Fri 10th Jun 2011 22:22 UTC
Permalink for comment 476970
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2011-01-28
acobar,
"Perhaps, I should have said it on a more direct style: I do not encourage people to write optimized code, I tell them to look for good algorithms and rather to good libraries whenever they are available."
I'm not sure what this has to do with my original post, but we seem to be on the same track.
"To me, actually, all this talk about the better language to code in is a bit misleading, we should clearly concentrate on algorithms."
Ditto.
"Sincerely, for most of the applications it does not matter a dime if you spend 1 millisecond or 1 microsecond doing something, and there are a factor of 1000 involved."
Well I actually disagree here, but that's just me.
"And for the ones that matter, there are a chance that it is already well known and that a wise compromise was devised."
Yes, by far and large, it is very difficult to write truly original algorithms because it's extremely likely thousands of other developers have tried to solve the same problems before us. However just because someone else has already done it dosn't strictly mean that we need to copy and paste every single line of code either.
"I see people everyday praising languages that make them write less code...And all those arguments are sensible."
Yes they are.