Back to the article's point...
I think here is the place for comments on the article itself, not The Reg's policy regarding ads :-)
I agree with Dan Clarke that it's a widely spread trend and mistake to make software development decisions at project level (such as language, platform...) based on technical tools we are familiar with. The author's example reminds us that software, just like any industrial product, should be designed and "packaged" for the targeted users, keeping in mind their expressed needs that motivated the software development in the first place.
Moreover I especially second his observations regarding language and machine interfacing technologies' evolution (ie. VMs). It's definitely allowing always higher levels of abstraction which makes developers' lives easier. This is extremely visible with the virtual machine based languages: the community of Java enthusiasts keeps on growing and delivering very friendly development tools (ie Eclipse) which drives this phenomenon, making it self-sustainable and continually evolving.