Yes, and that's a good thing if you don't want it to start killing processes. You have that extra time/space to deal with the out-of-memory condition yourself.
Or you can ignore that condition and continue using the system in a degraded state, with swap as "disk RAM".
No, but Windows is so entrenched that they don't need to actually be competitive in order to keep making profit. Instead, the Windows team has to invent things nobody ever wanted or needed that they can advertise to make it look like they're still useful. Software UX polish-passes don't make good marketing. You can't seriously put "you know that one weird thing that only happened to a fraction of users sporadically? we fixed it" on a marketing campaign.
Nobody. And it's not like Red Hat runs the X.Org Foundation, either, at most they have one seat on the board. Development will continue.
it'd be real cool if the mods of the biggest community on lemmy.world would actually do some moderating
ISP shittiness aside, ISPs do actually pay for Internet backbone access by the byte. Usually there are peering agreements saying "you take 1tb of traffic from us, and we'll take 1tb of traffic from you", whether that traffic is destined for one of their customers (someone on Comcast scrolling Instagram), or they're just providing the link to the next major node (Comcast being the link between AT&T's segment of the US backbone and Big Mike's Internet out in podunk Nebraska).
And normally that works pretty well, until power users start moving huge amounts of data and unbalancing the traffic.
I'm not sure what that post is meant to show, if swap isn't "disk RAM". That post even concludes:
Swap [...] provides another, slower source of memory [...]
PSoD is already used by VMware ESXi. And Windows Insider builds, I think.
Maybe green?
Yeah it's not very helpful. That page says "see the sidebar", when the sidebar is what pointed you to that page in the first place...
I think they're referring to the terms of service, which has a 5.0.1: https://legal.lemmy.world/tos/
If it's only on the ESP, it won't persist across reinstalls, and definitely not drive swaps.
But I do see mentions of attacking via firmware capsule. If that works, then yes, that will persist.
A singularity is the single point mass at the center of an ideal (Schwarzschild) black hole. But mathematically, that can only happen if the mass that forms the black hole isn't rotating. In reality, all the mass in the universe is moving around, because mass is not distributed uniformly, so gravity is pulling stuff around in a big mess. So when a black hole forms, it's definitely a rotating (Kerr) black hole.
A rotating mass has different gravity than a non-rotating mass. Not by much, but when you've got the enormous mass of a black hole, it becomes significant. This causes objects "falling into" a black hole to "miss" the point at the center, and form more of a cloud during spaghettification.
The article is fairly accessible if you sit down and read it.
Honestly, inside the event horizon, everything stops making sense compared to our day-to-day experiences. The immense gravitational forces distort space and time. It doesn't really make sense to think about objects remaining intact as recognizable objects once they cross the event horizon.
How? You could certainly temporarily break the boot process, but I can't see how you'd completely brick it.
No. They're literally a meme for how bad they are on tech content: https://knowyourmeme.com/memes/events/the-verges-gaming-pc-build-video