fritzy

Protestware is fascinating. It exposes that corporations depend on developers with no formal or informal relationship. It's also like that Daffy Duck cartoon where he performs a magic trick he can only do once -- you can get your message out or cause some damage, but after that, no one will use your tools anymore.

SteamOS is only going to support other hardware by coincidence. Valve is unlikely to put in resources beyond the hardware that they want to support. It's also unlikely to change the whole "firmware restore, entire drive" approach. They're not going to put in the resources or support work into making and maintaining a full distro by themselves.

A community distro (be it a console-like gaming focused distro or not) is going to be the way to be the way to go for the foreseeable future. I'm pretty happy with running EndeavorOS w/ KDE, Steam, and Heroic. The Steam client with Proton is where most of the magic happens in Linux anyway. If I wanted to get fancy, I could set up GameScope with Steam Big Picture to take a SteamOS/Bazzite approach.

There's similar projects like QB64 and L-Basic. I have to wonder if keeping language variants alive will be of historic significance hundreds of years from now. Will anyone care about early computing to this extent?

Ultima Online 2

I haven't had Firefox crash in years, and I use nightly for all of my day-to-day browsing. Chrome crashes or locks whenever I iterate on a canvas based game after some amount of refreshes.

OP's game hasn't flopped. The beta just launched yesterday and appears to be trending on steam and itch.

In reality, everyone works together to make sure the project is successful throughout its lifespan. It's not usually a hand-off.

I, the OP, am a starter myself. I was focused on finishers because they're often undervalued.

`table -> trigger to log table -> trigger to notify` is exactly the right solution here. You can even use the same stored proc to replay old logs.