creshal

By that point medicine will be sufficiently advanced that we can graft new fingers on him, obviously. That'll also make him more productive, given he's an emacs user.

All the code is kept in the rom, as are all the assets. So you only need to track sprites that move unpredictably, and the average 2600 game had very few of those - pacman, space invaders, etc have very few actice objects, and most of them are strictly constrained in how they can move.

doc vs docx is whatever, what kills older offices for me is the 64k row/col limit in excel. That was only fixed with the ribboned versions. :(

Especially when the following years once again confirmed that none of the big enterprise customers care enough to cancel any contracts over QA problems.

Sure, but compare that to the effort it would take to have the same safety guarantees without any drop in performance.

> Posted from a memory safe browser - WebKit MiniBrowser compiled with Fil-C. Pretty sure this is safer than even V8 and the heap sandbox.

It's easy to be safer, as long as performance can be sacrificed for it.

A lot of the stability problems come from trying to scale a free product on a still WIP cloud solution without costing too much; the same software running on separate, paid for infra has a lot better odds.

Which is a good fit to a distributed, offline first version control system, if you use it like that.

Microsoft considers it a bonus if a hype lets one department cripple another department.

IMO the constraint is that AI is still rather anaemic at sustainable green-field projects: It's good at one-off oneshots, and also at refactoring or fixing bugs or adding features to existing projects, where test suites and significant architectural scaffolding already exists, but the more you move away from that, the more wobbly the results get, and the more the human once again becomes the bottleneck, for all the hard work of coming up with all the conceptual scaffolding in the first place. Typing speed rarely was the bottleneck there anyway.

Reaching into ring -2 or the TPM allows privilege escalations past traditional "root permissions" and lets attackers defeat the sort of tamper protection that's designed to make escalations to local root manageable. Wipe-resistant malware, falsified cryptographic attestations, all sorts of fun.

Preferably one that doesn't deliberately shoot itself in the face to spite its users just to protect some committee members' egos.

Is C even worth saving at this point? Even standards committee members can't consistently write C code that doesn't overflow and segfault.

I'm always flabbergasted when I see what people pay and how much effort they need to invest to keep their cloud websites from eating them alive.

My allegedly more complicated VPS stack needs an afternoon of attention every two years when a new Debian major release is necessary, and costs have been predictable for 15 years, no matter what happened traffic wise.

I'm sceptical, where are all these essays he was supposed to have learned this very distinct style from? I certainly don't remember seeing them.