Sure! The core dividing line between the two books boils down to how they approach representing data in a program. Yehonathan's book advocates for immutable data stored in untyped data structures (for instance, Map<Object, Object>). My book takes the opposite approach. It advocates for building around immutable data that's strongly statically typed. It aims to capture the stuff in our domain using algebraic data structures.
This modeling difference has pretty far reaching implications. They lead to very different kinds of code bases, and thus very different books.
Here are the repos for the two books. Poking around those should give you a good overview for how radically two things both called "data-oriented" can differ :)
* https://github.com/chriskiehl/Data-Oriented-Programming-In-J... * https://github.com/viebel/data-oriented-programming