Seven Languages in Seven Weeks: A Pragmatic Guide to Learning Programming Languages (Pragmatic Programmers)

Perhaps the most impressive aspect of this book is that it teaches how to evaluate a programming language. The author has chosen 7 languages as the title suggests. For each language he describes different unique features of the language. Each language section is broken into three parts which are called Days.By reading this book you will not become an expert in any of the languages. The book is more like introduction to each language. Imagine you searched on Google for "Differences between Scala & Ruby". You would get the Wikipedia entry and maybe a blog post or two. This book is sort of like a really long blog post about the different languages.Bridging across chapters, the author looks often at the concurrency model each language has along with other aspects.It's not a perfect book though. Because the book is roughly 300 pages the coverage can be light, and clearly the author is not an expert in all 7 languages; but at least he does not claim to be... the author is generally humble throughout the book.This was the right book for me at the time, because I read it as I was getting back into software development. I wanted to know what had changed in programming as well, and it improved my knowledge.

Background: I stumbled across the author's blog post announcing his intention to write the book while looking for materials comparing language paradigms instead of particular languages (object-oriented, logical, functional, prototype, etc). The as yet unwritten book sounded like exactly what I was after (thus my enthusiastic anticipation). I purchased an electronic copy of this book from the Prag Press beta program about six months ago and began reading the chapters as they were completed and released. My paper copy just arrived from Amazon today. Thus I can comment on the whole content of the book and the physical object.Languages: While the languages covered (Ruby, Io, Prolog, Scala, Erlang, Clojure, Haskell) are excitingly (painfully?) trendy the list is not without merit. In the introduction the author explains that he arrived at the list by asking readers and edited from there: swapping Io for JavaScript and excluding Python thereby making room for Prolog. One could debate the choice of Io over JavaScript (particularly in a post Node.js / Common.js world) and make a case for including Smalltalk as the canonical OO language over Ruby; however, the chosen languages each bring something to the book and represent a number of interesting paradigms.Chapters: Each language has its own chapter. Each chapter has five sections: - an introduction to the language covering topics like it's history, place in the modern language landscape, paradigm, etc - 'Day 1' - 'Day 2' - 'Day 3' - and a conclusion with a few parting words / 'the moral of the story is...'.The boundaries between days are not particularly meaningful but roughly build from "here's the syntax" to "here's an interesting thing you can do with this paradigm". By Day 3 each chapter has moved beyond trivial "hello world" examples; not surprisingly then, the pace of progress is brisk and the details of how to get up and running with each language are largely left to the reader.Each language chapter includes an interview with a user/creator of the language (Matz, Steve Dekorte, Brian Tarbox, Martin Odersky, Joe Armstrong, Rich Hickey, Philip Wadler / Simon Peyton-Jones). These were an unexpected addition and quite worth reading. In fact, I wish the interviews had been longer and gone into more technical detail.In addition to the seven language chapters there is an introductory chapter that has the sort of information normally found in the pre-page-numbering introduction to a book (explanation of the book's contents, intended audience etc) and an excellent final wrap-up chapter (more on it later).Length: I easily completed each language chapter in a weekend. The first and last chapters are very quick reads. Seven weeks should be more than enough time to work through the book.Subjective annoyances: - The quality of the physical book (not great) will be familiar to regular Prag Programmer shoppers. It is not up to O'Reilly standards (it's more like an Apress book). Although the typesetting is easy to read the top and bottom margins are unpleasantly tight. The outside margin leaves room for notes which I like, but the book is awkwardly square. For $22 what does one expect? - Each chapter attempts creativity with a supposedly allegorical popular culture reference threaded through it (ex: Io = Ferris Bueller). I found these more distracting than informative. I'd include naming the chapter sections "day n" as similarly failed attempts and wish that instead attempting wit (ex Io Day1: An Excellent Driver) they had substantive names. Obviously this is totally personal opinion, you might like it.Outright Disappointment: I wish that the individual chapters went into significantly more depth comparing the motivations for and consequences of each language design. While the key features of each language are demonstrated with annotated code samples and explanatory text little is offered in the way of discussion comparing across language. For example the Scala chapter (selected at random) is on pages 121-166 in the index under "Scala" the only references outside its own chapter are found on pages 302, 303, 305-306, and 308 (all in the final wrap-up chapter). I view this as a real missed opportunity given the books unique approach/content. The final wrap-up chapter seems to be the only place with this sort of cross-language discussion and as a result it is both excellent and much too short.Conclusion: An interesting book that I enjoyed reading and expect to return to in the future. The physical book is of so-so quality and as such the electronic book may be the right product for you to buy. The missed opportunity (and loss star) are for a disappointing failure to draw cross-language comparisons within the text of each chapter.----------Update: [...]is a 45 min talk on the book / topics in the book.

Bruce Tate does an amazing job cutting to the heart of what makes seven programming languages special in about 50 pages each. He is also pretty honest about the limitations of each. I had a great time working through the seven chapters and learned a lot. At the start of each chapter, you have to figure out how to download and install a compiler/interpreter for your os. The book does not cover that part of the process which is fair enough. Then, each chapter contains a series of simple, complete, well-paced examples. Type them in, and be amazed how much you learn in 50 pages.This book is not (and never claims to be) a comprehensive introduction to any of the languages. In some sense it is better as it shows the strength of each, almost like an advertisement. He is trying to get you excited about each language. Going into this book, I had some familiarity with Ruby and Haskell but knew virtually nothing about any of the other five. On the two languages I had used before, those chapters were solid and I even learned a few things. Of the other five, Tate did his job and got me excited about Io. Since reading that chapter, I have been diving in to Io. The others were interesting, but Io caught my attention.The book is a little heavy on the functional languages: Erlang, Scala, and Haskell. Given that I am already Haskell fan, the Erlang and Scala chapters felt like a missed opportunity to me. Of course, everyone who reads the book would probably want a different list of seven.

I find this book to be a lot like "Programming Collective Intelligence" in that it introduces you to new concepts for even experienced developers. You're expected to know a lot about programming already, but as it's introducing new concepts, it gives you enough background to follow along, but not so much detail that you're bored. It also has a couple of different sections for each language, including short interviews with the language designers. You can learn ruby anywhere, but it's going to take you a while to find out what makes it unique, whereas this book gets right to what's important, with no boringness. You can get through one language a day, or faster if you don't bother trying to do the examples or questions, but those were well-chosen. The book is a little too playful at times (describing Ruby as like Mary Poppins), but it's entertaining and makes it less dry (ex. in a description of a possible mistake someone might make when programming Io it states "If that line of code is buried deeply into a complex package, Io just puked in your car.").

Working through this book was really enjoyable. It definitely taught me a lot and exposed me to lots of cool ideas. The author explains challenging ideas like monads in an incredibly intuitive and easy way. Unfortunately, the chapter on the IO language and the final section in the SCALA chapter are outdated.

Il faut prendre ce livre pour ce qu'il est: une exploration, une découverte.Au lieu de 7 semaines, il m'a accompagné 4 mois mais quel plaisir !Les exercices donnent vraiment du fil à retordre, mais une fois le voyage terminé, vous en garderez sans doute un beau souvenir.Voilà plusieurs mois que je tente d'apprivoiser la programmation fonctionnelle, ce livre m'aura beaucoup aidé.L'auteur a un style agréable et chaque nouveau chapitre est une vraie découverte.Un livre indispensable pour se cultiver ou se reconvertir. Mon profil: Je suis expérimenté en Java, Perl et PHP.

very good book.

This is one of my favourite programming books. It's also one of the books which has had a profound influence on me. I've read it cover to cover several times now.I've been programming for many years, and have also managed developers and teams of developers. But I've mostly programmed in C, C++, and Java (plus managed developers of the same). This book has opened my eyes to what else is available.On the first reading, I loved Ruby, quite liked Io, hated Prolog, liked Scala, quite liked Erlang, loved Clojure, absolutely hated Haskell. I bought Scala and Erlang books, coded a bit, and read loads of stuff on the web.On the second reading, I skipped Ruby (too much like good old C/C++/Java, although highly productive), didn't like Io, loved Prolog (amazing how it can solve a Sudoku puzzle on its own, just by telling it the rules), began to go off Scala (high gravitational pull from Java), loved Erlang, liked Clojure, and Haskell started to grow on me.As an aside - about this time I inherited a team which was working on an app which had been ported to Clojure, followed by the Clojure developers moving on. The remaining developers thought that their career had stalled, and they wanted to get back to the mainstream (Java). We found it almost impossible to hire Clojure developers. Please don't berate me on this - I like Clojure and its ethos, and the story says more about large IT departments than it does about Clojure.All of this Clojure, Erlang, and Haskell was getting me into functional programming. As a manager I'd been concerned about how we could get best value out of modern multi-core servers, and solve the seemingly intractable problem of how to code multi-threaded software in a reliable and developer-efficient way. Functional programming seemed to give some hope - especially Erlang.I read several Erlang books, and Joe Armstrong's (one of the designers of Erlang) PhD thesis. I bought and read Bratko's Prolog book, and even "Real World Haskell".Erlang is my absolute favourite language (and I like its syntax, so no great temptation to move to Elixir). Given its close relationship with Prolog, I need to get more into Prolog too. And Haskell has become a friend. I suspect I may end up being a Haskell developer.All this has been triggered by "Seven Languages in Seven Weeks". Thank you, Mr. Tate.

A proposta do livro é dar uma visão geral de 7 linguagens de programação atuais. As linguagens envolvem diferentes paradigmas e conceitos. Claro que não há aprofundamento, mas é ótimo para quem quer ter uma noção rápida e prática.