For driving development costs to zero.
HN user
stopdropnhotpot
Depends on the browser. There's standards here but not everyone is conforming.
There's all sorts of problems with the academic institution as it stands, but I don't think forcing anyone to retire at an arbitrary age is much of a solution.
But I agree that the problem with science starts there, in academia. The barrier to entry and the ideological loops you're asked to jump through; Well, you're told that's just how it is. Imagine carrying that attitude into your Scientific career because, well that's just how it is, if you want to be funded. Doesn't leave a lot of room for progression, only products.
I imagine Facebook uses highly monitored virts that are spawned and destroyed constantly. I really wouldn't call them "servers" more like instances or staging hosts for containers. Root exploits aren't so serious in a ethereal state..
Can you get away with ignoring Turing? sure. But it's not going to be a "great markup language"
Victims? Why would this requirement cause development difficulty? If anything it would make it easier to deliver, and a lot easier to develop alternative parsers for, and easier to extend as well. We figured out all these things a long time ago but then ignored them because we thought we knew better then those who came before us.
systemd is fine for single user systems and perhaps verts, but I would never deploy it on a server. The deprecation of cgroup v1 is a welcome change. It's come a long way, but it still has a very long way to go.
They're still predicting shift away from silicon is another 5 years out. No, really. It's been 20 years+ at this point they've been developing alternatives and they can make chips but they're far from being competitive with silicon in any metric. It's called single crystal complex oxide or SiC