Hacker News Reader

Comment by sliken | Hacker News Reader

I think of that as a win. Heavy software stacks create a demand for faster hardware and the market provides. Those of us with use cases that represent a tiny marketshare, but actually need the performance can do so with light software stacks.

So the question is, how can we make the overweight software stacks even slower?

View on HN

By going back to using interpreted languages. No more precompiled binaries where changing/adding patches and flags require full builds, just stream compiled/compressed source code directly to the target.

You could also extern the software to a webserver and only cache small parts of the software on the client. Instead of gigabytes of install sizes you'll be required to have a 1 or 10 gbit network link to run and stream features as you're acessing them.

Oh come on! No one would ever do that!... Oh wait

whistles in javascript

Coordinating that would be a nightmare. Interesting idea, though

Make it “industry standard best practice” to provide devs with absolute top end cutting edge hardware “for productivity and efficiency gains”. Repeat this at every opportunity at conferences and industry events until it becomes ubiquitous. Profit as devs slather abstraction layers, trivial libraries, emulation layers etc. on because “developer time is worth more than CPU time” and “it’s not slow on MY computer”. :D

Reply on news.ycombinator.com