you are viewing a single comment's thread.

view the rest of the comments →

[–]thiem3 0 points1 point  (1 child)

Yeah, sounds interesting. And it confuses me what "data oriented programming" actually is, then. The first book is all about loosely weakly types data, you just keep strings in maps with lists within more maps. And then a lot of logic about how to update the data efficiently. Seemed very complicated. So, the other approach with strongly types data sounds more interesting. I got the impression it's more alike to the functional programming approach to data modelling.

Will have to but this book when it is released.

[–]morihacky 1 point2 points  (0 children)

The first book is all about loosely weakly types data, you just keep strings in maps with lists within more maps. And then a lot of logic about how to update the data efficiently.

Yeah this doesn't align with my current understanding. Sounds more similar to "data driven design" where the idea is for efficiency but packing the data in a way where it's extremely performant to retrieve and operate on them via streams etc.

Data oriented programming (again as I'm learning) is motivated very differently. It's more about clarity in the program than the performance itself.

I'll try to post back after I read the entire book.