Generally a bad idea to use in-band signalling like that. They won't do anything weird but consider what happens if the actual data contains them.

Well I'm no fan of Python either but it doesn't describe itself as a scripting language (and neither does Ruby) so I think you're way off there.

And I dunno about Ruby being a better Python. It looks way worse to me. In particular the story for static type annotation seems pretty dire. The syntax is worse, it's less popular, and even slower!

I can believe the tooling is better though. Python's is abysmal (unless they officially adopt uv - ray of hope there but I have zero faith the Python Devs would make such an obvious decision).

Good luck with this approach on a server.

Indeed, obviously I'm talking about desktops here.

If by ‘suspend’ you mean that the process will just halt, then: Which processes? All of them? Good luck displaying a message then.

You could use some kind of heuristic to suspend ones using the most memory/CPU. Or just suspend them all. Obviously you would exclude the processes needed to display the message.

If by ‘suspend’ you mean moving the memory to disk

No I meant just pausing their execution. I'm pretty sure ctrl-alt-del does something like this on Windows.

Ah maybe. I'm still on RHEL8. Even so, "it hangs a bit and kills a random process" is still shit! What it should do is suspend processes, and show you a GUI saying "you're running low on memory, here are your running programs and how much they are using" and allow you to choose which processes to kill, or whatever.

That would be far too user friendly for Linux though. I don't think the kernel/Wayland Devs could really comprehend that tbh. They'll say something along the lines of "users shouldn't be doing that".

Not in my experience. Mostly it just hard-reboots. Occasionally a random process that is using lots of memory is killed (not necessarily the one you want). That only works about 5% of the time though.

Don't hard-reboot when memory runs out.

You basically shouldn't until you are forced to move. Almost all of the improvements so far are in the internal architecture.

You might notice some tiny differences if you switch, like logging in doesn't show a black screen at any point, and window choosers when screen sharing show a (totally broken) grid of previews instead of a plain list of window titles.

Hopefully when X is fully dead (give it another 10 years) we'll see some actual improvements, e.g. RDP-style remote desktop, good support for multi-monitor, HDR, HiDPI, etc.

Huge speed-ups for the will-it-scale tlb_flush2_threads test - presumably not very representative!

I wonder how much effect it has on real world workloads.

Funny because Rails is often touted as the main reason to use Ruby!

Definitely true for a minority. Not the way most of these articles are presented though (including this one).

I don't see why. You can be interested in Linux and like some aspects of it but still get annoyed at the blinkered zealots claiming that there's no reason to use Windows.

Pornhub's audience is 75% male, and Linux users are almost all male too (and ... no offence guys but probably more likely to rely on porn), so I wouldn't take that as a representative global figure.

Statcounter gives 1.4% which is much more likely to be unbiased (and sounds way more plausible based on my experience of real life).