If you’re branching logic due to the existence or non-existence of a field rather than the value of a field (or treating undefined different from null), I’m going to say you’re the one doing something wrong, not the Java dev.

These two things SHOULD be treated the same by anybody in most cases, with the possible exception of rejecting the later due to schema mismatch (i.e. when a “name” field should never be defined, regardless of the value).

You wish it was like that in the medical industry, but it absolutely is not

Buy a keyboard and monitor

And the only thing even worse than SCRUM is literally every other option

I just used it in the US last month, it definitely is.

Kinda dumb to do that when they already repair them for free (including shipping) with < 1 week turnaround.

No, that’s not how that works.

Users can generate their own keys, and you know it’s the same user as long as they have the same key, even if they’re on different servers.

No certificate authority is required for this kind of use case.

What this shows is how terrible raw JS is, when all of this crap is required to fix all of the edge cases and make things actually work the way it’s supposed to.