The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

boy18nj (112) [Avatar] Offline
#1
1)
As the reader reads from Page 3 to Page 4 sequentially, figure 1.1 shows up on the top. When the reader open page 4, suddenly it talks about bytecode- it confuses instantly momently a bit- not really big deal. The figure should be placed after its explanation.

Message was edited by:
boy18nj

Message was edited by:
boy18nj
boy18nj (112) [Avatar] Offline
#2
2)
Page-3
Is really Java used to build the basic infrastructure of servers?

I think infrastructure is the physical hardware used to interconnect computers and users.
boy18nj (112) [Avatar] Offline
#3
3)
Guiding Principle:
Java is great for tools, libraries, and infrastructure. Groovy is great for everything else.

It's like blunt statement. Not sure what is meant Groovy is great for everything else.
boy18nj (112) [Avatar] Offline
#4
4)
Page-7
Unlike Groovy, Java does not have native support for collections. So what's the point eventually collections support was added even if not native.
boy18nj (112) [Avatar] Offline
#5
Page-9

I provide the closure as the implementation of the Comparator interface.

I believe its Comparable interface.

Here I show the two
dummy arguments, s1 and s2, to the left of the arrow, and then use them on the right side.
What is the use of "->"
boy18nj (112) [Avatar] Offline
#6
Page-10

If the reference is null it invokes the size method here.

Why it will invoke the method on null reference?
boy18nj (112) [Avatar] Offline
#7
Re: Points I noticed-
Page-11 Java includes the checked exceptions.

What's the point here how Groovy helps us here.
boy18nj (112) [Avatar] Offline
#8
Re: Points I noticed-
Page-13

Can't tell from the code which is spread dot operator.
boy18nj (112) [Avatar] Offline
#9
Re: Points I noticed-
Page-16

Repetition of sentences in same context.

Example- No one is ever going to suggest rewriting Spring in Groovy.

Page-4

Nobody is ever going to rewrite, say, the Spring Framework, in Groovy.

No big deal.
boy18nj (112) [Avatar] Offline
#10
Re: Points I noticed-
Chapter-2

Page-19

Because every programming language book is required by law to include a “Hello,
World!” program, here’s Groovy’s version:
println 'Hello, World!'

I know what author means here. But it isn't law its custom tradition going on with every java programming book.
kenneth.kousen (57) [Avatar] Offline
#11
Re: Points I noticed-
Yes, of course. The "required by law" part was a joke, even if it isn't all that funny. smilie
boy18nj (112) [Avatar] Offline
#12
Re: Points I noticed-
Page-30

Because I’m working with Groovy,
and Groovy works well with XML, I’ll use the xml value.

It should be like this- Since I’m working with Groovy,
and Groovy works well with XML, I’ll use the xml value.

It actually confused me for a moment. I had to read the line twice.
boy18nj (112) [Avatar] Offline
#13
Re: Points I noticed-
Page-19

Groovy is all about simplicity and understandability.

I see the Groovy code is pretty tough to read/understand when it uses combination of collect, each, closure. Especially inside closures, when semi-colons are not used, it confuses it next line is part of previous line or new line. May be since I'm newbie to Groovy- there is a bit curve to learn.