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).
Sure, just like the “leakers” guessed it would come out last year, and the year before that, and the year before that… don’t worry, just keep moving that goalpost, you’ll get it right one day.
Yeah, this time the “leaks” are “different”, just like they were “different” last time, and the time before that, and the time before that, and…
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.
Using tools to break the encryption for backup purposes is legal in the US, but distributing tools to do so is not legal because the tools can be used for non-backup purposes.
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).