Hmm, seeing this type of reply makes me a bit sad :)
I think it's fine to advocate for the book, which is actually quite interesting so far, but, most working programmers will read it with the perspective of gaining new insights and/or better leveraging the functional style tools available in their working language, and not to "abandon" objects in any way, simply because it's not possible. Only a TINY fraction of us can use functional programming on our daily job or switch technologies completely.
I think most readers will approach this book with the idea of gaining new insights to apply to their daily work or simply to gain a fresh perspective.
There is no silver bullet, and if there is, it certainly won't be functional programming.... I mean the foundations have been laid out more than 50 or 60 years ago, so if it didn't take off into the mainstream industry in that time frame, it most likely won't now :)
Read the book and you'll be convinced 😁!
Hmm, seeing this type of reply makes me a bit sad :)
I think it's fine to advocate for the book, which is actually quite interesting so far, but, most working programmers will read it with the perspective of gaining new insights and/or better leveraging the functional style tools available in their working language, and not to "abandon" objects in any way, simply because it's not possible. Only a TINY fraction of us can use functional programming on our daily job or switch technologies completely.
I think most readers will approach this book with the idea of gaining new insights to apply to their daily work or simply to gain a fresh perspective.
There is no silver bullet, and if there is, it certainly won't be functional programming.... I mean the foundations have been laid out more than 50 or 60 years ago, so if it didn't take off into the mainstream industry in that time frame, it most likely won't now :)
Actually, in the book I show how to apply the principles of Data-Oriented programming to both FP or OOP languages.