Scala in Depth

I found this book very helpful while I was actively writing Scala (2014-2016). It really helped me and other members of my team to understand the edges of the language, how to use the best parts and how to stay away from the dark parts. For the Scala community, it played a role similar to Effective C++ (Meyer) or Effective Java (Bloch). It also helped me a great deal in learning to think functionally. I'm writing some Java these days and missing a lot of Scala features. I find myself looking back at this book regularly in order to hold onto that functional way of thinking and emulate some of these things in Java. Full disclosure: I know and worked with Josh. However that was long after I read the book. So my 5 stars stand!:-)

This well-written book will take you from an intermediate Scala programmer (where you understand and can apply all the techniques in Odersky/Spoon/Venners, say) to an advanced Scala programmer. When you have mastered it, you will have expanded your understanding of the language and your vocabulary of techniques greatly.Despite covering advanced approaches, the book is thoroughly practical. There are discussions of theoretical concepts such as type classes, monads and category theory, but here they are always application oriented.The book's main shortcoming is that it suffers from poor editing and typos. Also, more motivation for certain techniques is sometimes needed. For example, the discussion of type classes is very clear, but from the example that is given I could not immediately infer in what kind of general situation I ought to be applying the concept.Despite the shortcomings, serious Scala programmers should definitely get this book once they have a solid understanding of the fundamentals. It fills an important gap.

Best book on Scala I have read.It goes behind the surface, and explains that is happening inside Scala. Based on this understanding, it gives a useful set of recommendations and best practices. Definitely the book to get when you are ready to do something real in Scala.I gave it only 4 stars because it needs updating. It describes Scala 2.8, and an obsolete version of Actor.Still worth reading though

All the bad reviews are coming from the people that simply bought the book without even understanding the title! Of course this is not a beginner book and that is trying to be. I highly recommend this book. It saves you a lot of time in trying to figure out all the practices by yourself. Also the paper quality is really good.

The author has good intent, but the writing style is very dry and unnatural. It's a little awkward reading from sentence to sentence, and it takes a little extra time to process what the author is trying to say.3 might be harsh, I would give it 3.4 / 5

So maybe I'm just getting old...The text is small, and at least in my copy, gray rather than black -- the code is especially hard to read. No Kindle version??

The book is not for those who what to learn Scala. It's not clear the intend of author and there is no direction or flow in the book. It is written in most abstract manner, it is possibly the worst technical book I have read throughout my engineering career.If you are buying a book to learn Scala, stay away from this book.

Just started reading it, but seems to pick up right where Odersky's book leaves off. Seems quite readable and worth the money.

This book is intended to be a follow-on from books such as " Programming In Scala ". It concentrates on the "Why?" questions rather than just "How?", so if you are looking for an introductory Scala text, this probably isn't it. If you are are a Java developer the best way of describing this book is to say it's intended to be the Scala equivalent to " Effective Java ". It uses a similar style, being partly based around 14 "Rules for Improving your Scala Programs" listed inside the front cover. It explains how to combine advanced features together, such as Types and Implicits, as well as explaining any potential pitfalls that you need to be aware of. It is also the only Scala textbook that I've seen that attempts to explain Monads in any kind of detail.I'd like to say that this book should be on every Scala developer's bookshelf and that it will become a Scala classic in the way that "Effective Java" is for Java. However there's one huge problem. The book is completely riddled with basic proof-reading errors - spelling mistakes, code examples that are syntactically wrong and even entire repeated paragraphs. The forum for this book contains a lot of pre-print feedback on these errors, it is inexcusable that the publisher, Manning, seem to ignored them and printed a book that's so full of errors. I've tried my best to ignore them, but there are so many that in the end I've returned the book to Amazon for a refund - it just isn't what I consider to be acceptable quality for a book that's relatively slim (270 pages) and relatively expensive.Whilst this book fills a clear gap for users of Scala, it's has too many basic production errors for me to be able to recommend it in its current state. My advice is to wait until Manning publish a second edition, hopefully they'll actually edit the book properly as part of any such update. Programming In ScalaEffective Java

Wie alle Bücher aus der Manning-"in depth"-Reihe richtet sich dieses Buch an Leser, denen das Thema bereits hinreichend bekannt ist.Die Ausführungen sind stets nachvollziehbar (live in der REPL) und Designentscheidungen gut begründet.Schwerpunktmäßig werden neben anderen Themen komplexere Sprachelemente wie implicits, das type system, das Zusammenspiel vom implicits und type system beleuchtet.Die Umsetzung des Sacla-Codes auf der JVM wird bis auf Bytecode-Ebene diskutiert und sogar Auswirkungen von HotSpot werden mit in Betracht gezogen.Hervorzuheben ist der sehr pragmatische Style Guide (was hier wirklich positiv gemeint ist).Besonders empfehlenswert macht sich das Buch, da es die Collection-Library in der Version 2.9 beschreibt und die knapp dokumentierten (man könnte auch von fast nicht dokumentiert sprechen) Parallel-Collections beschreibt. (Nachtrag: Mittlerweile gut dokumentiert unter: [...])Man mag nicht mit allen Empfehlungen des Autors einverstanden sein, das schmälert die Qualität des Werks aber auf keinen Fall.Fazit: Lesen. Verstehen. Umsetzen oder Variieren.

This book was not proofread, and its examples often do not align with the text that tries to explain them. This book is hard to follow and contains numerous typos on every page.It is full of lots of useful information hidden away on convoluted code samples whose variable and type definitions do not match the text. You can learn a lot about Scala from this book, but it is written in an unnecessarily confusing manner.It seems to me like this book was rushed out to be one of the first Scala books on the market. It desperately needs to have a second edition to fix its obvious flaws.

Without question is the Author of this book very knowledgeable, and understands the topics presented in depth. However if you are looking for a book to help you be a better Scala developer, this might not help you as much as you expect. The topics presented feel disjointed, arbitrary and often lack a practical perspective on how the discussed points would map to real-life projects. While the Odersky book gives you a detailed view of language features, I expected this book to dive deeper into the topics of how to use these features, what the practical limitations are on readability, modularity and what features truly work, and which to avoid.If you just want to know more about random features of Scala, this book might be for you.

Libro decepcionante. Esperaba mucho más, pero se lía en conceptos hasta el extremo pasando por alto muchos más importantes. No me ha servido de mucho. Recomiendo functional programming in scala.