Linked by Thom Holwerda on Wed 24th Jun 2009 14:10 UTC, submitted by TuxJournal.net
Thread beginning with comment 370096
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.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2005-11-11
"I think is this kind of tolerance of the user that leads to developer care less to develop more efficient application. Saying go to get a more powerful cpu and more ram and you would get smooth experience is not the right way to solve problem. And that is why after so many years of hardware improvement, we still experience more or less the same speed feeling on desktop usage."
Which totally makes sense considering how expensive development time is compared to hardware costs. I can write an app in C in 200 hours and spend another 100 optimizing it to death. But why should I if I can also spend $40 on a hardware upgrade, and write the app in Python in 60 hours, which still performs acceptably?
A lot of people complain about this increase in "bloat", but I call it lowering development costs at the expense of increase resource usage. Considering that computers are meant to serve humans it makes total sense.
You may argue that open source software is free, so there's no "development costs". This is not true: the developer of said software may have invested tremendous amounts of time, which are also costs.