And why would they? They’re printing so much money, this niche probably doesn’t make a dent.

It doesn’t matter if Windows is the best system for gaming. It just matters if people believe it is.

You can always justify using Windows. “How do I get Game Pass to work on my handheld?” is probably something people care about.

Granted this is an expensive way to lock customers into your platform, but they’re already doing it anyways, so no need to pour money into the OS experience when you can just sell services building on customer data.

Allows you to scroll through / view a text file in the terminal.

I don’t agree with your assessment really as I don’t see the core experience declining.

But also, it’s a free project and people are putting in their time wherever they want; I don’t think the project would reject a submission for something based on “we’re doing too much” if it’s within the scope of a desktop environment.

From a quick glance, this is pacman with a yaml file instead of a shell script and PKGINFO (the latter was introduced for the same reason you’re doing it your way in the first place). The carcinization of package managers

For me, the factors were:

• the ability to split your system configuration into logical modules. Describe one logical thing in one file, no matter how many other factors are involved. Don’t want that thing anymore? Just don’t reference the module, and all changes will be reverted.
• easily try out new configurations and roll back, regardless of underlying filesystem, without performance penalties.
• the ability to put logic into your configuration (technically, there’s no difference between what’s typically referred to as configuration and a module in nix, though the latter usually has more “logic” and provides values with lower priority).
• as a consequence, make modules transferable between systems. There’s e.g. a Lanzaboote module that enables Secure Boot in a really smart way on NixOS, and the configuration is in my opinion easier than on any other Linux system.
• the reproducibility, from which the “easy reinstallation” follows

And from what I hear, the main selling point of NixOS is how easy it is to reinstall.

Well, that isn’t the first thing I’d mention, but whatever. Use whatever you’re comfortable with.

Did you try Nix (on Arch) or NixOS? For the latter, https://nixos.org/manual/nixos/stable/#sec-declarative-package-mgmt explains the basic installation.

I really like fish. It’s just so pragmatic, I don’t know how to describe it differently. No groundbreaking concepts (like nu or elvish), but the tools you need are right there and easily accessible with syntax that doesn’t make me scratch my head (bash).

TOTSUGEKI

It’s so funny because you look at the guy and think he’s fit. But I saw a video of him doing pushups and it’s honestly so unimpressive: https://www.youtube.com/watch?v=BOGNznbJPY0 like all that gear to not be able to do 10 full straight pushups? Ok dude

If you know that you want to play a game that only runs on Windows?

It’s their device, I never tried Windows on the notebooks I bought in recent years either

fsync isn’t faster than ntsync, it’s merely a workaround to match Linux to Windows synchronization primitives. From ntsync’s official description:

It exists because implementation in user-space, using existing tools, cannot match Windows performance while offering accurate semantics.

So without this, you either have a huge perfomance hit in case of an accurate implementation or you have good performance, but might run into edge cases where software doesn’t work well or at all because it’s not accurate (see https://github.com/ValveSoftware/Proton/issues/2922 for examples)

Unfortunately, from my testing back when I used Arch, a lot of packages in the AUR didn’t meet packaging guidelines, so while quickly writing a PKGBUILD is easy, writing it correctly requires a bit more effort, especially regarding the dependencies. IIRC namcap is often enough, but ideally packages should be built in clean chroots as well to make sure they build everywhere

Yes, nix complements your system’s package manager, but doesn’t replace it

Or am I incorrect. Is this just standardising the API in Vulkan and it gets forwarded to the same video encoding driver? Could we not have Mesa doing a better job? 😒

This is how I would read it. But if you have Mesa do it, it’s in software, and you might just be using a software coded directly then, it’s much easier.

From my understanding, it’s the hardware that produces bad results. There’s no encoding logic in the drivers itself. That’s why the encoding is accelerated in the first place.

E.g. if the hardware doesn’t support b-frames – which for long it didn’t – a new driver won’t do jack. This is just about how video data gets into and out of the card, any encoding logic is handled by the hardware.

On the last day actually, haha

For anyone interested, this was due to a curl regression AFAIK. 24.11 was supposed to release a week ago but a lot of stuff had to be rebuilt.

Kind of, it uses QtWebEngine. At least that’s the dependency on my system

Funnily, Konqueror is the first app out of the four to get adopted

Were you banned or shadow banned?

I was only shadow banned once, however never banned normally.