Wasn’t there a story about people calling curl devs because of car issues?
For what it’s worth, I’m sure the SQLite devs could help somebody clean up their temp files. They just really shouldn’t have to.
Wasn’t there a story about people calling curl devs because of car issues?
For what it’s worth, I’m sure the SQLite devs could help somebody clean up their temp files. They just really shouldn’t have to.
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.
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?
After loving Prey, I’m now playing Dishonored. So far so good, I like how quickly I was able to get zooming and target highlighting in lore appropriate ways!
There’s room for preference, I can enjoy a dark roast blend, but they seem to be really leaning into it these days.
Bad? Who’s to say. Specialty coffee is 100% Arabica and Arabica is more expensive to source, so, regardless of preference, I’m surprised by “100% the cheap stuff” marketing.
I think it’s an attempt to introduce apparent differentiation at a low price-point. I’m curious about future developments.
I love acidic specialty coffee that tastes like you squeezed half a lemon into the cup, but I also enjoy bolder, more classically intense coffee.
My main point isn’t so much about people’s different preferences, but the way companies seem to be pushing towards one end of the preference spectrum bit because of its value, but because of the cost and margins.
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.)
[flashbacks to the backlog being wiped out because “the client already signed off on the release”]