Can "Page's Law" Be Broken? 255
theodp writes "Speaking at the Google I/O Developer Conference, Sergey Brin described Google's efforts to defeat "Page's Law," the tendency of software to get twice as slow every 18 months. 'Fortunately, the hardware folks offset that,' Brin joked. 'We would like to break Page's Law and have our software become increasingly fast on the same hardware.' Page, of course, refers to Google co-founder Larry Page, last seen delivering a nice from-the-heart commencement address at Michigan that's worth a watch (or read)."
Nope (Score:5, Funny)
You just get an app which uses 100k of RAM and 32gb of filesystem buffer.
Re:The 'easy' way (Score:3, Funny)
Ah ha, the business model behind Android finally reveals itself :)
Re:Of Course (Score:3, Funny)
And this is often the curse of object-oriented programming. Objects carries more data than necessary for many of the uses of the object. Only a few cases exists where all the object data is used.
That sounds like bad software design that isn't specific to OO programming. People are perfectly capable of wasting memory space and CPU cycles in any programming style.
For example, I worked with "senior" (~15 years on the job) C programmers who thought it was a good idea to use fixed-size global static arrays for everything. They also couldn't grasp why their O(N^2) algorithm--which was SO fast on a small test data set--ran so slowly when used on real-world data with thousands of items.
Re:Of Course (Score:5, Funny)
I can't speak to emacs...
RTFM.
C-x M-c M-speak
Re:Of Course (Score:5, Funny)
agreed. Apple always manages to break it too with OS X. from 10.1 to 10.4 the OS notably improved in speed on even older equipment each time it upgraded, even on older PPC G3 and G4 machines.
Of course, when you're starting from a point of such incredibly bad performance, there's not really anywhere to go but up.
It would have been more impressive if they'd somehow managed to make it slower with each release.
Re:Of Course (Score:1, Funny)
I worked at a company whose CEO said the definition of real time programming was a program that ran "really fast".
I left that place as soon as I could.
Re:Of Course (Score:3, Funny)
That must be why there were dozens of threads updating and reading from these massive global arrays without using any kind of synchronization mechanism.
Shows what you know, they were just using classic Mongolian Actorfuck Model :)