The incentives are still there for churning out more and more code, compile it on more and more CI/CD pipelines, run it on clusters of more and more powerful machines, and interface it to more and more powerful computers in our pockets which have gigabytes of RAM, terabytes of storage, mad gigahertz multi-core CPUs but somehow still amount to being slow dumb terminals.<p>Damn, even open source world favors constant churn. New libraries come with breakage that demands every application out there to adapt with little to no reward, those applications aren’t becoming any better, they just keep chasing new languages, new frameworks, new windowing systems, re-solve problems solved long ago, and all of it is just to keep up.<p>Gosh, there was this comparison on how long would it take to cold boot a machine, open a document in a text processor, and print it out. The contenders were a 8-bit Commodore with floppies and a modern MacBook Pro. Guess what, while Mac won, it wasn’t by a wide margin at all. The Mac could likely easily emulate a dozen Commodores. Where are all the gains?<p>If I were to become a dictator of a large part of the world, I’d tax heavily all the extra cycles, all extra watts of power wasted, all extra RAM, and all excess bytes sent over the wire, and tax it enough to eat into profits of big tech. Incentives done right would make the developers think of efficiency from day one.<p>There’s also this thing that while we rely on tech more and more, we are just as far from actually automating the boring stuff away as we have been for the last 40 years. The stories about a plucky worker automating their job and not telling anyone are just as appealing today as they were two decades ago. And all this tech has bugs, is fragile, sucks big time and brings in a lot of frustration.<p>(Steps away from the soapbox and walks into the sunset.)