![](https://rblind.com/pictrs/image/65dca91c-dc2f-4373-ab2d-3e7ce631e80f.png)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
That’s the thing though, isn’t it? The devs on either side are entering into a contract (the API) that addresses this issue, even if by omission. Whoever breaks the contract must rightfully be ejected into the stratosphere.
Opinions are my own. Profile picture description: Black on white pictogram with a D20 showing 20 for a head and a game controller for a body and arms, holding a white cane.
That’s the thing though, isn’t it? The devs on either side are entering into a contract (the API) that addresses this issue, even if by omission. Whoever breaks the contract must rightfully be ejected into the stratosphere.
Thanks for the transcription!
Surely Java can tell the difference between a key with a null value and the absence of that key, no?
I mean, you can set up your deserialization to handle nulls in different ways, but a string to object dictionary would capture this, right?
Because they didn’t want to train their JS developers and didn’t want to cause friction for new projects. They get to say they’re using TS, with basically none of the real advantages. (Apart from general rational error checking.)
Yes, but did you get the job?
Also props for the image description.
Or “How Signal is closer in functionality to WhatsApp by the day, because it turns out people like the functionality of WhatsApp.”
Self-documenting code, high contrast… Carry on.
I was thinking about how this would happen and I remembered when signing up for services using Google login, I’d always get a list of information the website would have access to, including the name listed under the Google account. When I didn’t consent to that, I went back.
Now, is there a line somewhere between strictly getting a user’s consent and the user having an expectation of privacy? Yes, and they may have landed on the wrong side of it.
Suffice it to say, this is one of the reasons I prefer to sign up with an email address.
Risks that are already described.
The headline does it’s job getting clicks by making it sound like reviewers names may already be public.
I’m looking at it from a perspective of intentionality. Careless? Definitely. A risk ? For sure. But the situation is still not as the title implies.
If I’m reading this correctly, they’re adding your name to your site profile, but that’s not visible and is not linked to your reviews.
That specificity makes the situation much less terrifying than the title alone would imply.
Hey, you can cross-post this to rblind.com!
Found the Python developer. Hehe. Thanks for the reminder that we can do this stuff: all the common layouts are just suggestions, we can’t make our lives easier by recognizing that.
You were absolutely right! It’s been a while, huh? WhatsApp and Facebook Messenger are gatekeepers and WhatsApp is supposed to open up based on the Signal Protocol. I guess we’re settling on that.
A recall is the legally defined process to address a safety issue. From NTSHA’s documentation.
Manufacturers voluntarily initiate many of these recalls, while others are either influenced by NHTSA investigations or ordered by NHTSA via the courts. If a safety defect is discovered, the manufacturer must notify NHTSA, as well as vehicle or equipment owners, dealers, and distributors. The manufacturer is then required to remedy the problem at no charge to the owner. NHTSA is responsible for monitoring the manufacturer’s corrective action to ensure successful completion of the recall campaign.
There was a safety issue and it was addressed by the manufacturer: huzzah!
Even physical mechanical changes don’t usually require the car to go back to the factory, they’re often addressed as part of routine maintenance.
The term may feel misleading, but it exists and is used in a specific context.
No doubt, but MagSafe turning into the Qi 2 standard is… interesting. It may or may not be part of a broader shift.
Something something monopoly, something something gatekeepers. They don’t need a war chest big enough to sue Apple, they just need to convince the EU to do it. I’m sure they saw this coming from the start.
I have. I’ve accidentally initiated NameDrop between my personal and work phones, just by having them in the same pocket. Both set to Contacts Only.
Imagine a scenario where kids put all their phones in a bad before class or something.
A “technical limitation” is just a feature with a poor ROI on engineering hours on a spreadsheet. I mean, on Microsoft 365 Excel.
I think we’re fully in agreement here: if the API doesn’t specify how to handle null values, that omission means they’re perfectly valid and expected.
Imagine a delivery company’s van exploding if somebody attempts to ship an empty box. That would be a very poorly built van.