That’s Page as in Larry Page, of Google. His law is the inverse of the Moore’s Law: Software gets twice as slow every 18 months.
That’s why no matter how insanely fast hardware gets, your stuff never really feels any faster—it’s just matching the software slide. Of course, the reason Sergey’s explaining it is to explain how Google’s code is going to break “Page’s Law” and get more efficient and faster over time. Given where Google wants to be—on everything—let’s hope so. [Gawker]
matt
Monday, June 1, 2009 at 10:05 AMthere may be a couple of reasons for this lately, one being devs are trying to make multithreading apps, this is hard and there is quite a bit of overhead in getting your app to run on multiple threads. for instance, c, which natively supports all functions of a processor including the floating point unit, has no native support for multithreading. another reason could be that devs are using more and more middle-ware and high level languages such as .net (which is almost middle-ware in itself) there is always redundancy and unused functionallity when using lots of middle-ware, not to mention that most devs haven’t mastered the middle-ware they are using and this adds to the slow down.
SO HERES MY GRIPE:
if google were so adamant about performance, why would they only support JAVA on android? mobile devices need all the performance they can get, and they won’t even let us use a native language???
James McGill
Monday, June 1, 2009 at 7:10 PMSimple: Because C++ would require your app to be recompiled for every possible microcontroller. Cross compilation is a pain to manage.
Mobiles can increase Java performance using hardware based JVMs that do direct translation to microprocessor op codes. I don’t think the performance of Java is likely to be that big a bottleneck in this case.