No, that’s my point. Providing the builder factory as an abstract way to construct an entity, it is an abstraction. It removes you from the actual detail, that’s an abstraction. But it also introduces extra complexity, which in turn negates the value of the abstraction.

In reality, the intention is an abstraction, the result is often enough a bad abstraction that introduces more complexity and adds indirection.

To 1), that’s unfortunately not entirely true. The real abstraction criticized is more like introducing a StorableEntity layer that’s provided by a StorableEntityBuilderFactory. So instead of providing a compartment with a stable interface, they introduce a mess of generalizations.

Abstractions should be bulkheads, but in practice they’re often more like one of those beads-on-strings door decorations.

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 still don’t understand how all that infrastructure is supposed to be financed by just a handful of whales.

All those developers, analysts, designers, etc. could surely make more money in a proper business.

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.

You can go and buy sodium batteries already. They’re not competitive with Lithium ion batteries in many mobile applications, but very much competitive for everything where price is more important than size or weight.

Lithium has decades of research and industrial scaling behind it, it’s hard to break into that. But especially sodium is on a pretty good path to replace it in large scale storage applications.

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.

But I regularly throw a few handfuls of assorted pills and drive around the continent for a full weekend.

I literally can’t use that car!!!

Using the Rabbit R1 instead of generic ML was too obvious.

They also stated they won’t attack Ukraine.

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.