(1)

      $ curl http://alexott.net/en/fp/books/ 2>/dev/null | \
        grep -o 'http://www.amazon.com/gp/product/[a-zA-Z0-9]*' | \
        sort -u | wc -l

      132

Seriously, you've read 132 technical books, for 10 different languages, going back to 2009?

(2) I'm seeing books that have been OK-ish when they appeared and thus recommended by people, either because of lack of other choices, but also because the advice contained was the status quo, but right now are pretty bad choices. "Programming Scala", by Alex Payne, for example is an awful reference to put on any list of books for Scala. It contains bad practices, plus lots of references to obsolete parts of the standard library, not to mention its general flow is just awful. If you would have read it, you would have known. "Programming Scala" the one published by the Pragmatic Programmers, is another awful choice. Actually, all books on Scala published before 2010 are awful choices.

(3) What the hell does a book on Scalatra has to do with Functional Programming? Is it because the association with Scala or something?

(4) It's bad advice to tell people to buy books from Amazon. The E-Books are DRM-enabled Kindle versions, sometimes badly formated and you don't get the PDF. Many of those books have the same price if you buy straight from their publishers and you get both a DRM-free Kindle version and the PDF.

I read a lot & not all books were released in 2009-2013...

if you look to the page more precisely - it has a separate section, called Recommendations where only some of books are listed.

Regarding the Amazon - the 2nd paragraph clearly says "if possible" - nobody forces you to buy books from amazon!

Lets do the math - this isn't fiction we're talking about, it takes at least 2 weeks to read a technical book and this is assuming you can read at least 1 or several chapters per day, or maybe skipping chapters, which can't happen for many of those books, as some of them are pretty challenging and you have to think about what you're reading, you have to try out samples, you have to do extra reading to clarify stuff and so on.

But lets be generous and say that 2 weeks is the average for reading a technical book. And there are on average 52 weeks in a year.

    132 * 2 / 52 = 5.08

So that's 5 years worth of book reading, assuming that (a) you're reading each and every single day, without exceptions, without breaks and (b) that you aren't reading anything else. Why the heck won't you admit that you haven't read some of them and simply pasted links based on Amazon's recommendations or something?

Also, the section on recommendations is shallow. It references books for getting started, after which it gives advice to continue with the books above. And I'm not seeing negative remarks on the referenced books at all. Everybody has opinions on whether a book was good or not. What kind of review doesn't do that?

"Functional Programming in Scala" is an awesome book on functional programming btw. You should put that as a recommended book.

It doesn't take two weeks to read a technical book that covers material you already know. I have no opinion on the site's reviews, but it's completely possible to read hundreds of very technical books, as long as the material overlaps.

I at least briefly went through the almost all books before putting them into list (not counting early releases). It's not required to read every word in the book to understand what's in it.

I've heard about "FP in Scala" and it's loaded into my kindle prepared for vacation (together with many other)...