The year is 2030.

Computers boot directly into the browser. IDEs are just a web app now, running in the GPU. No one knows why. Or how.

All programs run in 4 nested containers on top of a hypervisor abstracting over the 5 major computational clouds. The last time a branch was predicted correctly, in any CPU anywhere, was 4 years ago.

Cloud costs are withdrawn directly from your retirement fund.

Ext7 just came out, it's written in Javascript and uses AI to guess what the file may contain.

@chrisg This fills me with as much despair as climate change.

@neia That's ok, they are basically the same thing.

Or, if that's too hot a take, they share common causes.

@chrisg Some days, I feel like we should go back like 15 years in computer hardware tech and just stay there for a few decades. Force developers to care about performance again. Force us to stop using so many layers of frameworks and indirection, move toward simplicity. Or at least stop the bleed a bit.

@neia Completely agree, and (shameless plug) I wrote as much in my small dbms manifesto

https://radiki.dev/posts/a-small-dbms/

TL;DR I hate the cloud and what it represents. I just want us to stop wasting all that energy, creativity and resources just to sell ads.

A Small Dbms

Software is political. All we can choose is what we say with it. And it’s time we started saying something new.

radiki.dev

@chrisg @neia Great post, thanks! A question, though. In my MediaWiki world "scaling" means that our wikis have millions of articles nobody cares about, but a few that get hit millions of times. Per second. And you don't know which.

I think this is similar in many software systems. Shops for example have a few bestsellers, or people buying the same stuff all at the same time. You don't want the system to crash exactly when you can make the most sales. Isn't this what scaling is about?

@thiemo

I agree that this can be one definition of scale. In my post, I talk about database scaling as processing large amounts of data. Not as the ability of a system to manage a large number of requests. That is a different challenge, that spans a larger part of the software stack. Databases are part of it, but doing that and managing petabytes of user data are different problems with different solutions and different implications.

@neia

@neia @chrisg I still lowkey miss the days where for speed on micro-computers your options were assembly or don't bother.