For many systems out there, /bin and /lib are no longer a thing. Instead, they are just a link to /usr/bin and /usr/lib. And for some systems even /sbin has been merged with /bin (in turn linked to /usr/bin).

Not just Linux… 99% of the time you see something weird in the computing world, the reason is going to be “because history.”

The C developers are the ones with the ageist mindset.

The Rust developers certainly are not the ones raising the point “C has always worked, so why should we use another language?” which ignores the objective advantages of Rust and is solely leaning on C being the older language.

They very rarely have memory and threading issues

It’s always the “rarely” that gets you. A program that doesn’t crash is awesome, a program that crashes consistently is easy to debug (and most likely would be caught during development anyway), but a program that crashes only once a week? Wooo boy.

People vastly underestimate the value Rust brings by ensuring the same class of bugs will never happen.

It really depends.

If I know I will never open the file in the terminal or batch process it in someways, I will name it using Common Case: “Cool Filename.odt”.

Anything besides that, snake case. Preferably prefixed with current date: “20240901_cool_filename”

People back then just grossly underestimated how big computing was going to be.

The human brain is not built to predict exponential growths!

Indeed. I would love to have a “modernized Morrowind” experience – an RPG game that really nails the role-playing part of RPG, but without the cheesy parts of Morrowind like the unintuitive combat system – but all of us know that it’s just not gonna happen.

If I remember right, the syncing issue was particularly egregious when you run windowed X11 programs on Wayland. So it could be that you got lucky.

I think if you consider anything post C++03 (so C++11 or newer) to be “modern C++” then Concepts must be the top example, doesn’t it?

Counting from C++0x that’s almost a decade of waiting.

It’s the explicit sync protocol.

The TL;DR is basically: everyone else has supported implicit sync for ages, but Nvidia doesn’t. So now everyone is designing an explicit sync Wayland protocol to accommodate for this issue.

You need to enable DRM KMS on Nvidia.

Mine is simply default KDE. The only visible thing I’ve changed is the wallpaper – changes to my desktop mostly concentrate on the “invisible” ones like shortcut keys or setting changes or scripting.

Desktop? I settled on Arch and Fedora.

Server? Debian. Although technically I never distrohopped on servers, been using Debian since the beginning of time.

Can’t replicate your results here. I play on Wayland, and deliberately force some games to run natively on Wayland (SDL_VIDEODRIVER=wayland) and so far I haven’t noticed any framerate changes except statistical noise.

It’s not a fork of wlroots. wlroots is a library to assist developers in creating Wayland compositors.

For what it’s worth, there’s XWaylandVideoBridge now which can allow screen sharing on XWayland applications.

Any “X11 vs Wayland” discussion will eventually devolve into a fight beteeen diehard X11 fans and diehard Wayland fans, lol.

I still won’t buy one just because of this news - they have done lots, lots of shitty things in the past. GameWorks, PhysX, Geforce Partnership Program, etc. While AMD is not exactly a saint when it comes to open sourcing, they still commit far more than Nvidia to open standards.

Debian is my go-to distro whenever stability is desired.

I use Arch btw (on my desktop), but I would never run it on my server… I feel that I could easily ruin my database (Postgres) if I am not careful enough with the rolling release.

Rosetta certainly does emulate* x86. It can dynamically recompile x86 instructions to ARM instructions, otherwise applications that include an x86 JIT wouldn’t work at all on ARM Macs.

* I know people will be pedantic about this… but other emulators (Dolphin, PCSX2 etc) have included a recompiler for ages and no one seemed to have a problem calling them emulators.