And Firefox Focus too!

Although that one might be a bit annoying for some users as it deletes the data after you exit.

Absolute madness. I cringe at the thought of making modern x86 asm code.

Great work!

Wait, what? Playstation?

C++ is at least backwards compatible (for 99% of code anyway, yes I know about some features being removed, but that’s an exception and not the rule).

AAAAAAAAAAAAAAAAAAAAAAAA

It’s just their ego showing through.

It basically now comes down to the current devs depending on new Rust devs for anything that interacts with Rust code.

They could just work together with Rust devs to solve any issues (API for example).

But their ego doesn’t allow for it. They want to do everything by themselves because that’s how it always was (up until now).

Sure, you could say it’s more efficient to work on things alone for some people, and I’d agree here, but realistically that’s not going to matter because the most interactivity that exists (at the moment) between Rust and C in Linux is… the API. Something that they touch up on once in a while. Once it’s solid enough, they don’t have to touch it anymore at all.

This is a completely new challenge that the Linux devs are facing now after a new language has been introduced. It was tried before, but now it’s been approved. The only person they should be mad at is Linus, not the Rust devs.

You’re mostly correct. People here don’t take Windows praise lightly.

NT is probably the best part about Windows. If you’re gonna complain about Windows, the kernel is the last thing to complain about.

As you’ve said, there are things that are still better about NT to this day;

• OOM conditions are way better - system continues to run mostly fine after emergency swapping memory pages into the page file. No crashes, just a freeze until the OS swaps stuff out. No data is usually lost due to this. Apps continue to run and you have the chance to save and reboot your machine.
• The driver architecture, as you’ve alluded to, is much more flexible. No need to rebuild a DKMS module every time the kernel updates. The drivers are self-contained and best of all - backwards compatible. You can still use XP 64-bit drivers on modern Windows (if you ever need to)
• Process scheduling is very good for anything equal to or lower than 64 CPU threads. Windows at its core can multitask pretty good on one thread and that scales up to a certain point.

Most of NT stigma comes from NTFS (which has its own share of problems) and the bugcheck screens that people kept seeing (which weren’t even mostly MS’ fault to begin with, that was on the driver vendors).

Mark Russinovich has some of his old talks up on his YT channel and one of them compares Linux (2.6 at the time) to NT and goes into great detail. Most of the points made there still applies to this day.

Not to mention - this isn’t necessarily the correct place for Windows anyway. That is exactly why they standardized stuff around Vista.

Plus - what about apps that store an ungodly amount data in there? Personally, I only keep the OS and basic app data (such as configs and cache) on the partition and nothing else.

Then something like Minecraft comes along and it’s like “humpty dumpty I’m crapping a lumpty” and stores all its data in “.minecraft” right there in your user directory.

Then you gotta symlink stuff around and it becomes a mess…

AFAIK LUnix exists as the “little Unix” project aiming to run on the Commodore 6502 computers.

There’s even a video where someone got it to run on a Famicom.

They kinda don’t have the sources there. That’s a decompilation by IDA in that image.

But nevertheless they could run it if they set up an arm64 machine, technically.