Piszę do Waszmościów notkę po angielsku, nie wiem, czy ostatnią na pewno pierwszą. Jednakże niech serca Wasze strachu nie znają, gdyż zamiaru przejścia na mowę tę zagraniczną nie planuję i wyrażanie myśli w rodzimym autoramencie kontynuować mam zamiar tak długo, jak Los łaskawy zapiski te prowadzić pozwoli. Skąd więc ten wybryk nie jaki? Otóż dłużnikiem będąc Szanownych Wydawców niżej opisanej księgi recenzję w mowie przez Nich rozumianej zamieścić zobligowany jestem. Niniejszym ino nadzieję posiadam, iż błędów i wypaczeń językowych sporo popełnionych nie zostało. Miłej lektury!
This note is in English (or Almost-Like-An-English) language, because this review should be readable and understandable also by Publishers of reviewed book, and this doesn't mean that I switch language of this blog to English. Also, I hope that it isn't too many language errors and mistakes. Enjoy!
This note is in English (or Almost-Like-An-English) language, because this review should be readable and understandable also by Publishers of reviewed book, and this doesn't mean that I switch language of this blog to English. Also, I hope that it isn't too many language errors and mistakes. Enjoy!
Some time ago I decided to use Groovy language in one of my project. Because it is my first Groovy project, I also wanted to read a good book about it. In courtesy of Manning Publications and Szczecin JUG I have opportunity to read first edition of „Groovy in Action”.
This book is split into three parts. First one is about language, second is about advanced features which coming with Groovy distribution, and third contains some hints and guides, which could help in day-to-day work with Groovy.
Cause, this book is about something new to me, is from „In Action” series and also I am „in action” with my project, I've read (and still reading) it with „in action” style. What it means? It means, that in given time, I'm reading this section of book which exactly I already need, instead of reading it page-by-page. Now I can say that with this book this kind of reading is pleasure. Easy-reading language (this is very important to me, as I'm not native English speaker) combined with easy-understanding examples makes learning about features of Groovy quite easy, interesting and enjoyable. Very good sectioning makes jumping through book (in case of looking forward or backward in our own learning process) content also easy.
What about content of book's part? I've read all of first part, cause knowing features of language is a basement of using it, and the only word which I can say about this part is „Great!”. It contains exactly what is needed to understanding how to use Groovy, what is possible to do with language, and how. After reading it I haven't almost any problems with understanding more advanced examples (found in other parts of the book, or in the web) at language level (logical level is other story ;)).
Second part I read more selective, so there are some sections at which I've took only a look (e.g. like most part of chapter about integrating). But in general, whatever I've read it is still in high level. Although sometimes it was quite hard to understand how something works without little help of external materials. I think, that in some places there could be more examples or more detailed explanation, especially in chapter about builders (This is powerful and useful feature of Groovy, but only reading and making examples from book is not enough to good understanding theirs idea, I think).
And at least, the last, third part. To be honest, I only take a short look at the most part of it. Why? Cause chapters are very specific. Cheat sheets or tips'n'tricks can be (and they are) useful quite often, but advanced Windows scripting or unit testing using JUnit isn't something important for me (as far as I don't script Windows or not use JUnit), so I only took a look, say „hmmm... okay...” and read something other (but if someone needs it, I think these chapters could be handy).
So, to sum up. A few years ago Phil Collins sang about groovy kind of love, today I can say that Groovy is kind of love. And this book is proof of this fantastic feeling (especially first two parts), even with its small weakness, which, I hope, will be polished in incoming second edition.
P.S. The biggest weakness of this book? It isn't in Polish, but maybe in future... Who knows...
This book is split into three parts. First one is about language, second is about advanced features which coming with Groovy distribution, and third contains some hints and guides, which could help in day-to-day work with Groovy.
Cause, this book is about something new to me, is from „In Action” series and also I am „in action” with my project, I've read (and still reading) it with „in action” style. What it means? It means, that in given time, I'm reading this section of book which exactly I already need, instead of reading it page-by-page. Now I can say that with this book this kind of reading is pleasure. Easy-reading language (this is very important to me, as I'm not native English speaker) combined with easy-understanding examples makes learning about features of Groovy quite easy, interesting and enjoyable. Very good sectioning makes jumping through book (in case of looking forward or backward in our own learning process) content also easy.
What about content of book's part? I've read all of first part, cause knowing features of language is a basement of using it, and the only word which I can say about this part is „Great!”. It contains exactly what is needed to understanding how to use Groovy, what is possible to do with language, and how. After reading it I haven't almost any problems with understanding more advanced examples (found in other parts of the book, or in the web) at language level (logical level is other story ;)).
Second part I read more selective, so there are some sections at which I've took only a look (e.g. like most part of chapter about integrating). But in general, whatever I've read it is still in high level. Although sometimes it was quite hard to understand how something works without little help of external materials. I think, that in some places there could be more examples or more detailed explanation, especially in chapter about builders (This is powerful and useful feature of Groovy, but only reading and making examples from book is not enough to good understanding theirs idea, I think).
And at least, the last, third part. To be honest, I only take a short look at the most part of it. Why? Cause chapters are very specific. Cheat sheets or tips'n'tricks can be (and they are) useful quite often, but advanced Windows scripting or unit testing using JUnit isn't something important for me (as far as I don't script Windows or not use JUnit), so I only took a look, say „hmmm... okay...” and read something other (but if someone needs it, I think these chapters could be handy).
So, to sum up. A few years ago Phil Collins sang about groovy kind of love, today I can say that Groovy is kind of love. And this book is proof of this fantastic feeling (especially first two parts), even with its small weakness, which, I hope, will be polished in incoming second edition.
P.S. The biggest weakness of this book? It isn't in Polish, but maybe in future... Who knows...
