In my experience it’s the other way around.

Sure, Java can tell the difference. But that doesn’t mean that the guy writing the API cares whether or not he adds a key to the dictionary before yeeting it to the client.

Indeed, and that turns out to be a problem if the JavaScript expects the key not to be there, but instead it is there. And then you try to tell the backend dev that the key shouldn’t be there, but he’ll try to convince you that it’s the same whether the key is not there or whether it’s assigned null and then you wonder if he’s messing with you, but actually he isn’t and then the only thing keeping you sane is bitching about it in meme form on lemmy.

Außerdem ist es nicht redundant, weil die Anbieter ihre Netze nicht untereinander teilen.

Du musst die Redundanz kaufen. Firmen machen das teilweise so und buchen bei verschiedenen Anbietern Internetanschlüsse. Die Freude ist groß, wenn man dann herausfindet, dass die Anbieter die Kabel doch geteilt haben und tatsächlich einmal falsch Baggern reicht, um beide Anschlüsse lahmzulegen.

π

If an attribute is null, I would prefer to simply not serialize it.

That’s interesting. I’m on the opposite team. If a customer model defines an optional birthday, for instance, I’d rather have it serialized as a null value if it’s not available for a specific customer.

To be fair, just because obj.foo is undefined, that doesn’t mean the key is missing. It could also be assigned the value undefined. const obj = { foo: undefined } vs const obj = {}

Hey, IT, I imported this data set twice, and now there are a lot of duplicates. Is there something wrong with the tool?

– Yes, that happened.

Sounds like any action move protagonist.

Nicht über Los!

Also gleich aus dem Fenster? Ein bisschen interessiert mich schon, wie schwer das ist und wie weh es tut…