Gamers complain all the time. I also don’t really have sympathy for billionaire publishers complaining about the one company not actively fucking consumers.

There’s still choices, you can buy from the Microsoft store, or publisher stores like origin or Uplay. Epic is a direct competitor, GOG is in a subset of the market like itch.io. Amazon sells PC games. There’s several streaming options as well.

PC gaming is a far more competitive market than your grocery store.

Government.

This is why I’m not a fan of REST, the whole as possible part is meaningless. It could be an api that’s 99% REST with a few well thought out methods for common actions that aren’t quite REST, or it could be a mess of an api that uses PUT occasionally.

Self documenting at an application api level is not really possible. What I’d rather have is consistency and predictability, which is impossible in a REST as possible system.

There’s also value in treating http as just a transport later. It can give you clear boundaries, 200 the app processed the request, anything else the app didn’t process it.

Yes most things are crud if you zoom out enough that doesn’t mean REST is just fine. The scope is larger now, the states are more complex and interrelated, relationships are more complex, data privacy laws can affect the physical implementation. REST also has a lot of baggage that leads to excessive bike shedding, or refusal to allow useful endpoints that aren’t sufficiently restful. Proponents also tend to be more concerned with the purity of the api than the usability and effectiveness of it

Yes I’d rather have a self defined standard that accurately covers the scope of an application and it’s use cases than stretch an old standard design for basic hierarchical text docs to work for a modern application.

The people that decide which rules are important or not when designing a “REST” api are generally insufferable as well.

I’d rather see this than actual rest or the more popular use the bits of rest that are convenient.

Same argument though, just a different value for the topic.

Any type safe language will help you prevent a wide range of bugs that non safe languages need tons of tests to detect.

ASP.net web forms were ahead of their time. I miss them every time I have to use modern js frontends.

Spite coding is almost the original coding.

It would have to be more like an unsolved mysteries show with a dramatic reenactment and a developer giving all the ugly details with a blacked out face and voice changer.

Printers are solved now, you just don’t have one.

They aren’t context aware, it’s using statistical probability. It can replicate things it’s seen a lot of like a tutorial regex. It can’t apply that to make a more complicated one. Regex in the wild isn’t really standard at all, because it’s rarely used to solve common problems. It has a bunch of random regexs from code it analyzed and will spit something out that looks similar.

If you know even a little about how an LLM works it’s obvious why regex is basically impossible for it. I suspect perl has similar problems, but no one is capable of actually validating that.