I know that this topic has not been posted for lots of days and probably closed, but I have to write it somewhere to chill out.
I've bought this book recently in anticipation to find a simple way for a noob like me to learn how to make games using SFML in C++. Thats all I wanted. So I started to study this book. I ended up spending more time debugging and stitching together incomplete or sometimes even missed code presented in the book, rather than focusing my mind on the game making of things. Currently I am on page 39 and what can I say... I find it difficult to follow as book's focus is shifted more towards fancy C++ tricks rather than SFML game making ... Boy the author made it so damn difficult. I understand the author knows C++ subject in depth and good at it, and that is alright. BUT GOD DAMN IT! If I wanted to buy a book "Learn how to go ballistic with C++ coding" or "How to be hardcore with C++ OOP and templates" I would look for that specific book!
Author, mate, whats wrong with you dude? If you want to show off your C++ skills or knowledge of different C++ standards, you could have just written a separate book about that, without killing the joy of making games, correct? Why didn't you just wrote a book about making games using SFML and simple C++, and focus on actual SFML game making with short examples and results on the SCREEN? Man I am on page 50 of your book and I still see that small blue rectangle in black window, that does not move and does nothing at all LOL
... Damn that is discouraging my brother...
Please C++ coders, may I ask you please, if you write books about Games making write about Games making (no need to kill the fun of making games with hardcore C++ tricks), or if you want to write about deep C++ OOP and templates write a separate book just about that, just do not mix it with the fun of game making in C++... Do not get me wrong, its all common sense, if you write a book about apples do not write about cats.
Thanks.