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.

The grand unified file.

The price at all is ridiculous. Touring a rental is a sales action. Yes you have to pay for someone to administer a tour, but that’s a cost of doing business. It’s also weird because you generally don’t pay to tour homes for purchase.

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.

I’ve seen that as a bit by a comedian before as well.

After having kids I totally understand how it can happen by mistake.

Spite coding is almost the original coding.

Part of that is a legal issue. People over 40 are a protected class, you can’t discriminate against old people for being old. Young people can get fucked though.

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.

Not nearly to the same degree, and most colleges have no problem kicking out domestic cheaters.

Harvard is private, there aren’t out of state fees. They do pay significantly more than American students, which is why universities are fine with ignoring the rampant cheating from foreign students.

I discovered even worse recently. The office i went to added a third party wellness company to the new patient sign up process, so you were agreeing to their payment policy then next page is a nice dark pattern to join some bullshit company.