Not sure what you mean - “Mario and Princess Beach” is obviously peak cinema

I’ve had good experiences with my Nvidia card on Aurora (same basis as e.g. Bazzite), but HDR is indeed still an issue.

Right now, all you have to do is go to the settings of your non-steam game, go to compatibility, and choose a Proton version. I’m not sure if this change will automate it, but it’s pretty much as easy as it can be already.

I’d interpret that as a local social network app, not map/navigation.

Oh, you should have mentioned that - or do you think that fsck is Memtest? It is not.

Hm, unfortunately nothing obvious. And your last boot ended with a crash?

Nevertheless you could try running a Memtest (this can take a while) - it will check whether any of your RAM modules are faulty: https://www.memtest.org/

That’s unfortunately a bit cut off. Could you run this again with the following command? sudo journalctl -xeb -1 --no-pager

Sure, though the immutable design makes it very safe to touch these things.

OP, do this - it’s the best way to figure out what’s happening. It could be any number of issues, e.g. faulty RAM. With the output of the command above people can tell you what to test for.

JS itself is great, I prefer it to most other languages due to the flexibility that it allows. Adding types through TS to safeguard against footguns doesn’t mean you’re not still using JS. You can also add the types using comments instead if you prefer it, which means you’re actually writing raw JS.

That’s your prerogative, but it honestly doesn’t make sense. Typescript adds almost no functionality to JS (and the few pieces it adds are now considered mistakes that shouldn’t be used anymore). It only focuses on adding typing information, and in the future you’ll be able to run TS that doesn’t use those few added features as JS (see the proposal).

You can also add the TS types as comments in your JS code, which IMO shows that it’s not a different language.

Not really, considering Typescript only adds static types to JS. It’s not a different language, it’s an extension.

I wouldn’t use raw JS for anything new, yes. Typescript however is an excellent language.

Sure, but at this point it’s your own fault if you don’t use Typescript to keep these issues from happening.

There is operator overloading happening - the + operator has a different meaning depending on the types involved. Your issue however seems to be with the type coercion, not the operator overloading.

It should not happen no matter why it does happen under the hood.

If you don’t want it to happen either use a different language, or ensure you don’t run into this case (e.g. by using Typescript). It’s an unfortunate fact that this does happen, and it will never be removed due to backwards compatibility.

Sure, but then your issue is with type coercion, not operator overloading.

It should just randomly pick any “1”. Add a bit of spice, you know

That’s the case in many languages, pretty much in all that don’t have a separate string concatenation operator.

I don’t know, plastic feels fairly unnatural

As such we had to install openrgb the usual system-wide way, with rpm-ostree in terminal - something I was hoping he would never had to do.

There is nothing wrong with doing that if there’s no better option. You’re not losing out on anything.