ace

Oh I am more than capable of complaining about both. Like RedHat again fucking over the community and making our life even more troublesome, or the electronics software company using the RedHat ESR duration as their release timeline due to support requirements for their certifications.

I definitely agree with your second point, but unfortunately there are big software companies which don't.
The main software package which we have to use for our electronics courses only supports RHEL as one example - and currently only RHEL 7 at that.

I work as a Linux sysadmin for a university, we're paying for a full RedHat site license with all the goodies, and we certainly feel royally screwed over by this.
Not every single piece of software we run is a RedHat developed/sanctioned thing, and the removal of a guaranteed bug-compatible development platform for the people building those pieces of software - without jumping through hoops or limiting development efficiency - mean that we can no longer guarantee that core pieces of our infrastructure software will remain available for our RHEL installs. Not to mention course IT, where things are even worse in that regard. Lots of such software is already developed/tested/packaged on Alma/Rocky, and if they start diverging from being RHEL bug-compatible - which is very likely with this change - then we're going to either have to switch away from RHEL - and the paid support, or lose support from the pieces of software.

We're probably going to have to move a bunch more of our ~1.4k systems off of RHEL and onto things like SUSE, Debian, etc in the near future, just so that we're ready for when shit really hit the fan.

Websockets really don't integrate well with the entire rest of the HTTP stack, instead just repurposing the socket as a free-standing two-way communication pipe.

You can definitely use websockets for requests like regular HTTP, but you have to reimplement things like cookies/session handling, request resumption/retry, duplicated request detection, request timeouts, authentication, etc yourself if you want to use it that way.

I personally much prefer regular HTTP requests for queries/RPC, and HTTP SSE for notification streams, since those are well developed technologies in the web space - and work much better if there's a middleware in between.

We're in the end times now.

Still far too new a game, thinking of something from before the second millennium.

Deranged jazz and cool shades.

Psychonauts?

If you search for https://beehaw.org/c/programming instead - a.k.a. the URL instead of the Lemmy-syntax of [!programming@beehaw.org](/c/programming@beehaw.org) - then you should find it as a "person" on Mastodon. Messaging to that "person" is the same as creating a new post in the community, replying to one of its boosts is the same as commenting - or replying to a comment.

Dungeon Siege (2002) is a nice RPG; 3D, isometric-style default camera, slightly tactical order-based movement/attack, and a fully streamed world - so no loading screens during gameplay.

It certainly has its fair share of jank as well, but it does well otherwise.

Are you planning to also do something like the Black & White multiplayer mode?

This actually looks surprisingly good, will definitely have to check it out once released.