Uh, there are an absolute fuckload of Java libs out there with nothing more than auto-generated garbage Javadocs.

I dunno, plenty of those sound pretty reasonable.

Why are you such a piece of shit? Or is this just bait?

Sure, perhaps it’s possible that I saw an unusually high amount of apologists, but I’m saying that it happened enough times and consistently enough that it prompted me to block them before I even knew anything about them, which I think at least says something. I won’t claim to know what the majority opinion there is, but I don’t think it’s a stretch to say that it’s an abnormal amount.

Answer me this: are they or are they not consistently in support of Russia/China? Because I’ve seen it a lot from them (and blocked the instance soon after joining Lemmy when I noticed the pattern).

Is it just some big joke that went over my head?

I dunno, I ended up blocking the instance way before I knew about their reputation (like, when I first joined Lemmy) because all of the users their kept posting the most unhinged shit.

I have definitely seen blatant apologism for China/Russia from them.

FWIW, I’m much further left than your average Democrat (I consider myself a leftist/anarchist). I personally don’t consider what I’ve seen from them to be very “left”, just authoritarian.

All it means is if you were to reverse the order of the characters, you’d get the same string you started with. So “dog” isn’t a palindrome because when you reverse it, you get “god”. “dog god” is a palindrome, though, because if you read it backwards, it’s also “dog god”.

It’s not complicated at all: https://en.m.wikipedia.org/wiki/Palindrome. Not really something that’s education-specific, in this instance (though I suppose it’s commonly used in entry-level programming classes since it’s a simple concept).

Same story for Nebraska. Most of the population lives in Omaha or Lincoln which both lean blue, but Republicans gerrymandered the fuck out of our districts so we’re a red state. And it matters a lot more here since we’re one of two states that split our electoral college votes by congressional district. Like recently Lincoln overwhelmingly voted for a Democrat for our district in a special election, but Republicans naturally redrew the fucking maps to include counties that are fucking north of Omaha (like 120 miles away). Look at this shit: https://www.google.com/maps/place/Nebraska’s+1st+Congressional+District,+NE/@41.2698636,-96.4887192,8z/data=!4m6!3m5!1s0x87915d2ef259455b:0x74cb97568fa3047a!8m2!3d41.5312936!4d-97.2652858!16zL20vMDl0eHky?gl=us

Oh, if you worked at a company that uses them (which is a lot of companies), you’d definitely be familiar with them as they hog up a ton of fucking CPU/disk. I basically had an entire CPU core dedicated to running their bullshit.

After working at a company that had Crowdstrike installed on all machines, it is most certainly malware.

It depends on the country. This is true in American English and it’s what we teach in schools. In British English (which, in my experience, is what most ESL learners outside the US end up learning), they go outside the quotes. Source.

Why in the ever-loving fuck would it do that? My hatred of Go only continues to grow.

It has the return type declared to be double.

That’s what the If-Match header is for. It prevents this problem.

That being said, I generally think PUTs are preferable to PATCHes for simplicity.

It’s about making APIs more flexible, permissive, and harder to misuse by clients. It’s a user-centric approach to API design. It’s not done to make it easier on backend. If anything, it can take extra effort by backend developers.

But you’d clearly prefer vitriol to civil discourse and have no interest in actually learning anything, so I think my time would be better spent elsewhere.

As I already said, it’s very simple with JSON Patch:

[
  { *op": "replace", "path": "/Name™, "value": "otherName"}
]

Good practice in API design is to permissively accept either undefined or null to represent optionality with same semantics (except when using JSON Merge Patch, but JSON Patch linked above should be preferred anyway).

The semantics of the API contract is distinct from its implementation details (lazy loading).

Treating null and undefined as distinct is never a requirement for general-purpose API design. That is, there is always an alternative design that doesn’t rely on that misfeature.

As for patches, while it might be true that JSON Merge Patch assigns different semantics to null and undefined values, JSON Merge Patch is a worse version of JSON Patch, which doesn’t have that problem, because like I originally described, the semantics are explicit in the data structure itself. This is a transformation that you can always apply.

Zalando explicitly forbids it in their RESTful API Guidelines, and I would say their argument is a very good one.

Basically, if you want to provide more fine-grained semantics, use dedicated types for that purpose, rather than hoping every API consumer is going to faithfully adhere to the subtle distinctions you’ve created.

Only if using JSON merge patch, and that’s the only time it’s acceptable. But JSON patch should be preferred over JSON merge patch anyway.

Servers should accept both null and undefined for normal request bodies, and clients should treat both as the same in responses. API designers should not give each bespoke semantics.