data-oriented-programming

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-programmi

My book "Data-Oriented programming" is #1 Manning best seller for 2021. The book formulates the principles of an approach to data that reduces complexity and illustrates how to apply them in a statically-typed language like C# or Java or in a dynamically-typed language like JavaScript, Python or Ruby. Here are the 4 principles of Data-Oriented Programming: 1. Separate code (behaviour) from data 2. Represent data with generic data structures 3. Data is immutable 4. Separate data schema from data representation It might sound like Functional Programming but if you look closer at the principle list, you will notice that principles #2 and #4 are not part of FP. For those who already bought the book or are interested, I released the book's source code to https://github.com/viebel/data-oriented-programming. The publication is expected for March

Here you go: https://github.com/viebel/data-oriented-programming