Not for you. And certainly not for the staff working in the shop.

Currently, you’re bartering with copious amounts of copium.

… And if the systems you actually interact with go down, you can get fucked as well.

If you want to buy food with Monero and the payment processor for the local shop doesn’t work, even if it’s a local machine sitting in the back office, you still can’t buy anything.

Bitcoin lightning is absolutely hilarious. Your solution to Bitcoins problems is - not using Bitcoin. Wow, galaxy brain move.

The energy cost to maintain the base chain is <1% of global energy use, mostly from renewables

Yeah, that’s bullshit. First of all, 1% of energy use for a network that serves a few million transactions per day is really bad. A single 1kW node in Visa’s datacenter churns through that in an hour.

Second, it’s not renewables. It’s everything they can get for cheap. And that’s often enough coal, gas, oil. Also, they’re driving up power demand as a whole, which means fossil energy is actually needed longer.

Repairability doesn’t really matter if you only get two years of software updates.

Yes, there’s lineage OS, but whether their support will be better, is doubtful.

We shouldn’t support a company that openly says they don’t give a crap about their users’safety.

Wife of a friend as well. She’ll bend and “interpret loosely” every rule in her favor, but if someone else is doing the same, she gets mad and thinks it’s cheating.

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.

Prudes…

Java’s Duke just stands there, fully nude and is giving NullPointerException fucks.

I get the sentiment, though.

Some places define “toxicity” as anything a millimeter away from the party line or any debate at all. And it’s just annoying that someone can abuse their power to silence everything they don’t like.

Communities like this turn into Pleasentville.

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.

That sentence had several aneurysms.

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.