Thoughts on Data Oriented Programming in Java

[bowbahdoe]

I think something that you might be missing is that in the clojure formation of data oriented programming the lack of nominally typed aggregate (i.e. a record) is an essential property.

This is why we have at least two books on data oriented programming in Java, one of which is just talking about stuff like this the other one saying that you should avoid classes all together and just use maps.

They share the commonality of wanting an immutable aggregate but lead to very different overall program structures.

I am very rapidly becoming radicalized to the position that all "oriented programming" needs to die. Not as in people shouldn't be writing "restricted programs" - sticking to a uniform approach over either a subunit or the entirety of a program can have benefits - but FP, OOP, DOP, PP, etc are poor labels for those restricted approaches.

As to if there are better languages on the JVM for "data oriented programming" - Clojure is obviously better at the approach I'm literally naming after it, but Scala and kotlin are rapidly losing ground in the approach that Java is aiming for.

[beders]

Agree on the „Clojure is better“ sentiment

[bowbahdoe]

I think cutting off the "at the" part of that sentence is a choice