No, just realising the ones we have based on assumptions from the 70s don&#x27;t match what we really want.<p>My phone has an operating system that mostly pretends that it&#x27;s a mainframe. With just a little hardware, I could hook some circa 1978 VT100s up to it and a team of average *nix web backend developers could even be productive.<p>My &quot;workstation&quot; pretends to be several tens of machines doing all sorts of different things. These boundaries exist for no reason other than to map to organizational concerns -- my CPU does all kinds of computational gymnastics so I can &quot;keep things tidy&quot;.<p>The model is just wrong. Things are immutable that shouldn&#x27;t be. Things are mutable that shouldn&#x27;t be. Things aren&#x27;t distributed that should be. Things aren&#x27;t durable that should be. Things are shared that shouldn&#x27;t be. Things are isolated that shouldn&#x27;t be. Config management, containers, orchestration, stuff like adding BPF to the kernel, Docker, Hadoop, Mesos -- all very cool, but all very much bandaids.<p>We&#x27;re working on it but because we&#x27;re human we can&#x27;t go straight for the goalpost, we have to play politics, cheat by modeling the future using what we already have today and lead by example.