Prudes…
Java’s Duke just stands there, fully nude and is giving NullPointerException fucks.
Prudes…
Java’s Duke just stands there, fully nude and is giving NullPointerException fucks.
That is absolute nonsense. SUSE mostly serves large enterprise customers.
And where do you think the people deciding what to buy get their information? Mind share is important.
I’m pretty sure SUSE is bigger than Canonical.
That’s actually surprising to me, but I’d argue that Suse offers more products, it seems like Rancher, Longhorn, etc. have no canonical equivalent.
Reboots after three days and then disappears in the cloud.
And you really think, people who are willing and able to buy enterprise support for their Linux distro get confused by the naming? Sure, there’s that one confused dude, but you also have people asking Facebook where they left their keys.
OpenSuse is essentially free marketing for SUSE, nobody would know them otherwise. Why would you give that away?
Suse is not a huge company, it has neither a large enterprise backer nor any killer features, and its market share is relatively small compared to Red Hat or Canonical. Throwing away free marketing while alienating a relatively passionate community is a kind of brainrot only MBA can come up with.
Is there even someone left?
I only tried it around 2008 or so and it was extremely slow paced back then while looking like the interface from a sci-fi movie.
Or requires a timestamp with zone offset, but ignores the zone offset, so you have to send the timestamp itself with a zone offset of zero relative to the systems timezone, but can’t just omit the zone offset, because it’s required.
Again, did you actually read the comments?
Is SQL an API contract using JSON? I hardly think so.
Java does not distinguish between null and non-existence within an API contract. Neither does Python. JS is the weird one here for having two different identifiers.
Why are you so hellbent on proving something universal that doesn’t apply for the case specified above? Seriously, you’re the “well, ackshually” meme in person. You are unable or unwilling to distinguish between abstract and concrete. And that makes you pretty bad engineers.
Did you read the comments above?
You can’t just ignore context and proclaim some universal truth, which just happens to be your opinion.
Nope.
If there’s a clear definition that there can be something, implicit and explicit omission are equivalent. And that’s exactly the case we’re talking about here.
None. The project was ultimately cancelled for unrelated reasons.
I had lengthy discussions about that because two companies conventions collided.
We talked literally hours about the benefits of build numbers, branch specific identifiers and so on.
I find it really weird that something as simple as the basic functionality of nextcloud seemingly can’t be implemented in a stable and lightweight manner.
Nextcloud always seems one update away from self destruction and it prepares for that by hoarding all the resources it can get. It never feels fast or responsive. I just want a way to share files between my machines.
There are other solutions, I know, but they’re all terrible in their own way.
That’s exactly not the thing, because nobody broke the contract, they simply interpret it differently in details.
Having a null reference is perfectly valid json, as long as it’s not explicitly prohibited. Null just says “nothing in here” and that’s exactly what an omission also communicates.
The difference is just whether you treat implicit and explicit non-existence differently. And neither interpretation is wrong per contract.
It can, but especially during serialization Java sometimes adds null references to null values.
That’s usually a mistake by the API designer and/or Java dev, but happens pretty often.
I would really like to know what is happening inside such people’s brains.
Is this just a deflection or is this his actual belief? Or is it just schizophrenia?
Using the Rabbit R1 instead of generic ML was too obvious.
Well, yes, but the underlying issues still persist, so it’s not exactly a sustainable strategy.
I have to say, I’m getting more and more frustrated by the bad code I have to write due to bad business circumstances.
I want clean, readable code with proper documentation and at least a bit of internal consistency and not the shoehorned mess of hacks, todos and weird corner cases.
They re-invent everything for no reason. Every mundane device has been “re-invented” using big data, blockchain, VR, now AI and in a few years probably quantum-something.
The entire tech world fundamentally ran out of ideas. The usual pipeline is basic research > applied research > products, but since money only gets thrown at products, there’s nothing left to do research. So the tech bros have to re-iterate on the same concepts again and again.
That’s decades of legacy for you…
I bet each step/arrow/decision had a good reason at some point, but most of them probably back when computers lived in caves and hunted their tapes using spears and rocks.
I feel like we’re slowly reaching a point where the complexity is collapsing in on itself - just look at the absolute chaos a modern web app is.