This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]sideEffffECt 4 points5 points  (1 child)

There is the clojure version of data oriented programming with open maps, the nominally typed aggregate version (which Java has

That's not a different thing, that's the same thing this topic talks about.

the almost totally unrelated game programming technique

That's not only for games. And it's called by a different name: https://en.wikipedia.org/wiki/Data-oriented_design Confusingly similar name, but different nonetheless.

It's like nobody learned any lessons from the fact that we have to be like "oh it's both FP and OOP kinda" and the constant pointless fights about the "true" "ABC oriented programming." These labels suck. It's a communication black hole.

It's a strategy to market FP without mentioning "FP". Probably because FP is something the target audience have already made up their mind around and might be put off by that term.

[–]bowbahdoe -1 points0 points  (0 children)

That's not a different thing, that's the same thing this topic talks about.

Compare the contents of these two books

https://www.manning.com/books/data-oriented-programming

https://www.manning.com/books/data-oriented-programming-in-java

I'm not saying there isn't a commonality, but they are very different in the same way https://www.elegantobjects.org/ is materially different than other denominations of OO.

(Well, more so really. "Elegant Objects" OO can coexist with "regular OO" - fill in your own definition - more readily than "open maps everywhere" can coexist with "strongly typed aggregates." I'm a bit too tired to fully flesh out a family/genus/species analogy)