Joe Gregorio wrote a short reaction to Beyond Java which I'll use as the starting point for my own reaction.

I got a review copy of Beyond Java some time ago. I feel a little bad because I didn't review it. Frankly it didn't hold my interest; I mostly got it because I was told I was referenced in it (it was a footnote link to this post). And of course it was an uphill battle for the book, since I have never used Java and am largely indifferent to the platform.

What the book lacked was any useful exploration of what is beyond Java. Instead it was essentially some email exchanges with people about what they thought the advantages of other environments were. Lots of the people referenced didn't have very strong backgrounds outside of Java, or didn't really speak as anything more than an advocate. I expect more measured and thoughtful responses out of a book; the web can provide me with whatever advocacy I desire. There should be some point to getting a book over reading blogs. I suppose it's not Bruce's fault that the blogs win out here -- I'll attribute that to the ever-increasing quality of discussion on blogs, and books just aren't keeping up.

There's a lot of material to explore when you venture beyond Java. It's not all good out here. There's whole new ways to mess up. And maybe the details are beyond the scope of the book, but it's a whole book, not a blog post that should try hard to stay under one screenful. There's room for some good details.

For instance, here's a bit of advice: using a new sexy technology can be a strategy to bring great developers to your shop. Often the new technology is a buyers market for the employer -- developers want to use it, but most employers aren't even considering it. But the new technology becomes less new, the novelty wears off, and the developers may very well notice that the work they are being asked to do sucks, and they will leave. Or to phrase it another way: you can pay a great developer enough and give them enough freedom to start on a lifeless soul sucking project, but you can't make them stay. Do you think your project is actually worthy of great developers? For a lot of Java shops that answer is probably no. (You can't get them to live in Detroit and work on payroll systems either, even with a cool language and hip development methodology.)

(As an aside, and as a Python developer: you can keep your dumb jobs, you can keep your proprietary community, you can keep your enterprise, because please don't come bother us with your boring enterprisey problems)

Beyond Java didn't really talk about stuff like this. I can't believe it's because of a lack of knowledge, wisdom, and experience around these issues either -- but this knowledge isn't (by definition!) in the Java community where Bruce Tate probably hangs out.

I was going to react to Joe's original post, not just the book, particularly whether Beyond Java asked the right question. But because I think that reaction is more interesting than this review I'll do that separately.