I see Endeavour as Arch with sane defaults. They also use the Arch repos, if the distro dies I’m not really affected.

deleted by creator

I would be okay with defective controllers if Nintendo bothered to fix them. Through the entire lifespan of the console they sold controllers that would eventually drift. I own 3 pair of joy cons, they all drift. When sent for repair they were all deemed unrepairable, even those under warranty. That’s inexcusable.

In the new iteration of joycons they STILL don’t use TMR or hall effect sticks.

I don’t want to support this company.

I was hoping for a 700/800 euros TBH. 1k is kinda pushed since this is going to be marketed as a console, a kinda underpowered one at that.

I bought the Switch 1 on launch and loved it, it was everything I was looking for on a console. However, every single joystick broke. I bought several joy con packs and they all drift heavily. Even the pro controller drifts. Nintendo Iberia refused to even repair them. They gave me the option to either replace them with a 20 euro discount or pay 20 euros for them to ship them back.

Awful product quality, awful support, zero accountability. Guess what, I’m spending my money elsewhere.

Correct me if I’m wrong but isn’t cachyos deploying the exact same solution? The only difference seems to be that their package manager offers to swap the packages.

These are the official drivers, it is just a pinned version that won’t be updated anymore. It should work as well as it did before the switcheroo.

AMD cards have support directly in the Kernel, its usually plug and play. You just have to be careful about brand new cards (ie: released very recently) to ensure your distribution of choice has a new enough kernel and mesa.

No need to reinstall the entire os, just swap the driver packages…

Have you tried the aur package mentioned in the Arch News? https://archlinux.org/news/nvidia-590-driver-drops-pascal-support-main-packages-switch-to-open-kernel-modules/

I don’t see why it wouldn’t work with wayland.

I’ve been excited to try this out but I don’t have the functionality yet.

No email service can refuse to obey the law. None.

Proton is at least non-profit now.

I also played ff8 before ff7 and largely prefer it. The combat system is a mess but I’ve grown to like it.

I played a bunch of HoMM 3 but I don’t think I understood how to really play the game. That game is a lot more complex than it initially seems and it’s not trivial to me when to add new heroes, explore and split your units.

I like the rolling updates, to be honest. Endeavour has been a wonderful and simple experience. Aside from some NVIDIA issues with Wayland it has been a blast.

Lightning Returns was boring AF. I tried to play it like 4 times but I just can’t. It’s awful.

13-2 is one of the worst ones, to be honest.

Final Fantasy X is probably my favorite Final Fantasy of all time. Just don’t play X-2, assume the story ends immediately.

The HD remaster has some “cheats” to smoothen your experience, if you ever want to give it another shot:

• No random battles
• Infinite gil
• All non key items
• invencibily (to make up for low levels)

This way you can enjoy the story and move quickly through the game.

If you don’t enjoy turn based battles nor grinding I think this IP is just not for you. Definitely nothing before Final Fantasy 12. Maybe Final Fantasy 12 is ok, though I thought the story was on the weak side.

But you can’t look at a method signature and instantly know who handles the null check. You need to inspect code and calls to know for sure. This will lead to paranoia, sooner or later

The problem is that when an project is too big and a method is called from multiple contexts it’s very easy to lose track of the context where the null check has been done and where it hasn’t. This leads to a lot of duplicated null checks around the project and the constant paranoia of “can this be null here?”.

A much better way of doing this is using the Optional when an Object can be “null” and a direct instance where it cannot. This way, at any given context you know for absolute sure if a null check is needed or not. However, even with annotations this does not throw a compile error…