News for hackers. Stuff that matters.
Re:Android doesn't use the GPU for its UI by stavros on Sunday September 12, 2010 @05:52PM (#1684644)
When were computers fast enough? Each computer I've gotten is exactly as fast as the previous one, from the 100 MHz pentium I had in 97 to the quad core I have now. Programs do more things, but that's why the speed has remained the same.

My only hope that this will change is with SSDs. I swapped my laptop's SSD for a HDD and now it's a dog, which reminded me how big the difference in performance is.

Re:Android doesn't use the GPU for its UI by mikeryan on Sunday September 12, 2010 @06:23PM (#1684710)
My anecdotal experience is different from yours. In the early 2000s I finally reached a point where I generally didn't care if my computer was the newest/fastest kid on the block. But of course Your mileage and usage may vary
Re:Android doesn't use the GPU for its UI by angusgr on Sunday September 12, 2010 @10:23PM (#1685255)
I agree with your overall point, but I think your memory might be tricking you a bit. Mostly because the improvements have been gradual, and you've come to assume them.

Your subjective impression of speed probably hasn't changed, but I bet if you dig out your '97 Pentium and fire up Windows 95, you'll be surprised at how it compares to your memories of using it.

Re:Android doesn't use the GPU for its UI by 10ren on Monday September 13, 2010 @10:38AM (#1686692)
Allow me to answer in terms of integrated vs. modular architectures: they were fast enough when Java's virtual machine became viable, when .Net's virtual machine became viable, when interpreted scripting languages (Javascript, Python, Ruby) became viable.

Basically, whenever an extra layer that soaked up performance in return for other benefits (such faster development time, better error checking, more flexibility, easier, more intuitive) was actually adopted by real people, it meant that the computer was fast enough in their opinion to trade some of that fastness for other benefits.

relevant: http://xkcd.com/676/

Re:Android doesn't use the GPU for its UI by 10ren on Friday September 17, 2010 @03:49PM (#1702577)
Garbage collection (mentioned in the article) is also a great example of integrated vs modular, with the same tradeoffs: when you handle it manually, it is integrated with the code - and it's possible to optimize/customize its performance much better than an automatic garbage collector.

An automatic garbage collector is a separate module: the details are separated from your code; different garbage collectors (with different strategies/tradeoffs) can be used without affecting your code; and development is cheaper.

Re:Android doesn't use the GPU for its UI by kiba on Sunday September 12, 2010 @06:17PM (#1684699)
The average programmer skills probably stay constant but the average line of code is dependent on how many programs have versus how many lines of code they accumulated so far. However, you can bet older products will have more features by the virtue of code accumulation. With carelessness of some programming team, they become slower. Others, being more careful, will remain the same. Still others, gain in performance with practices that allow them reliable improvement in code quality.

Programs might have done more stuff, or not depending on what software you're looking at. Browsers on the whole do more stuff, but they also do it fast and efficient.

The evolution of software is much more dynamic and tricky to figure out. They are like corporations. Some corporation accumulate bureaucracy, others remain so-so, and others shed accuracy as a matter of survival.