http://cacm.acm.org/magazines/2009/5/24648-spending-moores-d...
Microsoft Research has a version of the article (not exactly identical):
http://research.microsoft.com/pubs/70581/tr-2008-69.pdf
I also discuss this in my (unfinished) book, with lots of data:
http://www.amazon.com/Objective-C-Performance-Tuning-Develop...
The whole book is / will be (well, the manuscript is) full of examples of techniques that are 2x, 10x or even 100x slower than necessary, but now "recommended practice", often for no discernible benefit.
* Increased functionality
* Increased programmer productivity (programmers are often more scarce than available CPU cycles)
* The bottlenecks have changed
The thesis being challenged in grandparent (pjmlp):
> It applies to the bloat in software development nowadays with layers on top of layers that seldom add any real value to the product.
implies that we are just being wasteful for no real benefit, but we are obviously getting more functionality in or writing more software via increased programmer productivity. Now that power is more of an issue for mobile, we are seeing programmers be more thrifty again, but that is not without a cost in productivity.
- Compiling to a VM + JIT instead of AOT compilation
- Running a programming language VM with an OS agnostic runtime, on a OS VM running on a hypervisor, instead of running the said programming language VM on top of the hypervisor directly
- Use of data structures and algorithms that take much more memory and are slower, because many developers lack proper knowledge to use the right ones and use whatever first result comes on their IDE completion suggestions
Just a few examples out of my head.
Sun tried this and the code actually got slower.
> Running a programming language VM with an OS agnostic runtime, on a OS VM running on a hypervisor, instead of running the said programming language VM on top of the hypervisor directly
Flexibility to run on a VM is a huge time saver.
> Use of data structures and algorithms that take much more memory and are slower, because many developers lack proper knowledge to use the right ones and use whatever first result comes on their IDE completion suggestions
Cheaper (less skilled) programmers means more code can get written (for better or worse).
Who is speaking about Java here?
Optimizing compilers for other languages are a proof that AOT compilation at the end wins.
> Flexibility to run on a VM is a huge time saver.
Of course it is, we just don't need the huge amount of layers the current VM cakes have. Software needs to go to the gym.
> Cheaper (less skilled) programmers means more code can get written (for better or worse).
Ergo less quality that leads to software bloat like Wirth states.
Worse is better. At least better than nothing.
Other than that, I stand by my point that modern software has lots of bloat of useless layers.