Even then there’s rarely a good reason to use inheritance instead of composition.

I’M FUCKING DYING

In that extremely rare case I just delete the offending characters from my long generated password or add a couple randomly.

It’s been a while since I used Windows, but back then my company blocked the Store, so I couldn’t install the Terminal through that. But it was easy to install through the released msix package - maybe you can install that through Winget?

Seems like a perfect use case for a password manager.

I’ve literally never had an issue with password generation. Usually I generate 32 character passwords with all types of characters passwords on average expect. If a page has different rules, I just check the corresponding boxes in my password manager, and I get one that works for that site.

I can’t recommend password managers enough, because you will never have this issue again.

Why don’t you send me even more replies over the next few days, I’m sure that will be really helpful!

Sure, that was cleared up a couple hours ago when OP clarified as such. Since texture apparently wanted to argue (given his many comments posted long after the clarification), I thought I’d play along for him.

Yep, I’m being serious, Fedora’s decisions don’t affect Arch.

And yet, Fedora changing their default login manager won’t affect Arch.

Quickly in Bazzite, not at all in Cachy since that’s based on Arch.

It’s Gnome. They do actually keep removing stuff that they disable by default, because they don’t even offer a GUI to configure these settings.

Ah, bummer. Looks like they don’t provide a Fedora repo, otherwise it would have been easy to layer onto Silverblue etc. There’s probably still some way, but I get not wanting to go through that trouble.

Out of interest, which client is that?

And that’s why I immediately fell in love with immutable distros. While such problems are rare, they can and do happen. Immutable distros completely prevent them from happening.

Yes, there exist different kinds of type safety. What the fuck are you even asking?

Sure, never claimed anything different. Runtime type safety != type safety.

There are plenty of libraries to provide type safety at runtime.

Yes it is? It isn’t strictly sound, but it is type-safe aside from explicit escape hatches (which other type-safe languages also provide).