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).

Buy a keyboard and monitor

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

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.

If you get ghosted, it only proves that that person is emotionally immature and wasn’t ready for a relationship anyway, so they did you a favor by outing themself.

This is not useful now, nor will something like this ever be useful.

The damage was not the actual pricing (which was cheaper than Unreal), the reason people are going to leave for Unreal/Godot and never come back is the loss of trust. Nobody wants to be chained down to a company that’s willing to pull the rug out like this.

Except Unreal already had the same kind of pricing structure that Unity is trying to move towards, that’s why Unity thought they could get away with it.

If you think they had impenetrable security before this, I’ve got some bad news for you…

Any time a gaming company does something stupid, leave it to gamers to out-stupid the company and prove that they deserved to get shit on in the first place

Vivaldi will never have it

No, it’s not in Vivaldi

Vivaldi doesn’t (and won’t) have it.

Of course they can. Everyone knows that password managers exist.

The driver is always responsible for using the tools within the car correctly and maintaining control of the vehicle at all times.

Either way the driver would be at fault. However, the driver might be able to make a (completely separate) case that the car’s defects made control impossible, but since the driver always had the option to disable self-driving, I doubt that would go anywhere.

Just like you don’t get off the hook if your cruise control causes an accident… and it doesn’t matter how much Tesla lied about what it may or may not be capable of, because at the end of the day it’s always the driver’s responsibility to know the limitations of the vehicle and disable the feature and take control when necessary.

It’s the API that ALLOWED the misuse in the first place, so the developers are the ones to hold accountable.

Sounds like the heuristic is taking multiple samples only uses them if they are within some consistency threshold, to hedge against the cases where the field has random data.

The reason it only fails rarely and randomly is because it only happens when multiple actually random timestamps happen to line up around the same time.

Sort of like how several applications (cough git cough) have failure modes when two different files happen to have the same hash.

Turns out developers are bad at statistics and probabilities and don’t understand the birthday paradox.

You need to get a cert from Let’s Encrypt (using certbot), then look up directions for configuring nginx to use the cert files generated by certbot.

The problem is that almost all electronics available online (not just on Amazon) are rebranded Chinese bargain bin garbage marked up by 10x and people think “it must be good because it’s expensive”.

Really your only option is to either accept that everything is disposable and will need to be replaced frequently, or to find the “good” brands and stick to them.

That last part is by design… it’s why a lot of this shit is perpetuated by the same parent company under a different name, to create a “hostile environment” to make it so you can’t shop around for cheaper prices.