Beyond Java and over one million other books are available for Amazon Kindle. Learn more

Vous voulez voir cette page en français ? Cliquez ici.


or
Sign in to turn on 1-Click ordering.
More Buying Choices
Have one to sell? Sell yours here
Start reading Beyond Java on your Kindle in under a minute.

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Beyond Java [Paperback]

Bruce A. Tate
4.0 out of 5 stars  See all reviews (1 customer review)
List Price: CDN$ 34.95
Price: CDN$ 29.21 & FREE Shipping. Details
You Save: CDN$ 5.74 (16%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Usually ships within 2 to 5 weeks.
Ships from and sold by Amazon.ca. Gift-wrap available.

Formats

Amazon Price New from Used from
Kindle Edition CDN $11.82  
Paperback CDN $29.21  
Save Up to 90% on Textbooks
Hit the books in Amazon.ca's Textbook Store and save up to 90% on used textbooks and 35% on new textbooks. Learn more.
Join Amazon Student in Canada


Book Description

Oct. 2 2005 0596100949 978-0596100940 1

Bruce Tate, author of the Jolt Award-winning Better, Faster, Lighter Java has an intriguing notion about the future of Java, and it's causing some agitation among Java developers. Bruce believes Java is abandoning its base, and conditions are ripe for an alternative to emerge.

In Beyond Java, Bruce chronicles the rise of the most successful language of all time, and then lays out, in painstaking detail, the compromises the founders had to make to establish success. Then, he describes the characteristics of likely successors to Java. He builds to a rapid and heady climax, presenting alternative languages and frameworks with productivity and innovation unmatched in Java. He closes with an evaluation of the most popular and important programming languages, and their future role in a world beyond Java.

If you are agree with the book's premise--that Java's reign is coming to an end--then this book will help you start to build your skills accordingly. You can download some of the frameworks discussed and learn a few new languages. This book will teach you what a new language needs to succeed, so when things do change, you'll be more prepared. And even if you think Java is here to stay, you can use the best techniques from frameworks introduced in this book to improve what you're doing in Java today.


Product Details


Product Description

About the Author

Bruce Tate is a kayaker, mountain biker, father, author, and Java programmer inAustin, Texas. His five books include Better, Faster, Lighter Java and the bestselling Bitter Java (Manning). His 17 years of experience include stints at IBM, two failed startups, and his own independent consulting practice called J2Life, LLC.


Inside This Book (Learn More)
Explore More
Concordance
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index
Search inside this book:

Customer Reviews

5 star
0
3 star
0
2 star
0
1 star
0
4.0 out of 5 stars
4.0 out of 5 stars
Most helpful customer reviews
4.0 out of 5 stars A quick and informative read Dec 21 2005
Format:Paperback
This book is great if you are looking for a compact, informative book focused on life after Java. It is written from a survey level, meaning that to get detailed information on most of the topics in the book (e.g., OO scripting languages like Ruby, web frameworks like Ruby on Rails, and continuation servers) you will have to look elsewhere. But this is a good place to start to whet your apetite on these subjects to decide if you even really want to invest more time.
One of my favourite aspects of the book is how Tate includes snippets of interviews with other well-known people (often other authors), like Jason Hunter and Erik Hatcher. I appreciated seeing multiple perspectives on the issues.
I would have liked to have seen a little more discussion on the .NET platform. Even though Tate dismisses C# as a Java clone, ASP.NET is definitely nicer to work with than Struts. And where I live it is becoming more popular and many shops that were using Java before are switching to .NET. Whether or not this makes sense is another issue, but more insight into the current situation and future of .NET would have been great.
Was this review helpful to you?
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com: 3.7 out of 5 stars  29 reviews
101 of 103 people found the following review helpful
3.0 out of 5 stars Interesting, but narrowly-focussed, error-ridden and frequently annoying March 29 2006
By Michael Vanier - Published on Amazon.com
Format:Paperback
There is a lot to like in this book, and a lot not to like. I'll talk about the negatives first and then discuss the positives.

The style of the book is extremely annoying. The author is a kayaker and a mountain biker, and he introduces each chapter with a kayaking/mountain biking story meant to serve as some kind of analogy to the programming topics he'll cover in the chapter. I found this unnecessary and distracting (I don't need sugar coating on my technical reading), and it felt like the real purpose of the stories was for the author to demonstrate how cool he is. In addition, the author uses the phrase "a perfect storm" over and over and over to describe the factors that led to Java's position of dominance in the programming world. I hated that expression even before I read the book; it has to be the most abused expression of the last few years.

Despite the fact that the book is ostensibly about programming languages, the author is by no means an expert on the subject. To his credit, he admits this freely, but he also makes numerous small and not-so-small mistakes when describing programming language features which may lead more knowledgeable readers to wonder if he's really qualified to write this book. For instance, in several places he describes the advantages of static typing as being mainly for early error detection, without also pointing out another big advantage of static typing: faster code (there are other advantages as well). In another place he makes the blatantly false statement that "Smalltalk is where all the continuation research is happening", ignoring the fact that Scheme (a Lisp dialect) has had continuations since 1986, and that there has been and continues to be active research on continuations in Scheme ever since. Then he says that "In Lisp, everything is a list." Wrong again. He also seems to assume that statically-typed programs will always be verbose, indicating that he is unfamiliar with statically-typed languages like Objective Caml which have type inference. The bottom line is that he often doesn't know what he's talking about when he compares the features of different programming languages.

The author's programming expertise appears to be primarily in the domain of small to medium-sized web applications. This is an important domain, but it's far from the only programming domain. So the book's subtitle "A Glimpse At the Future of Programming Languages" should really be "A Glimpse At the Future of Programming Languages for People Who Exclusively Write Small to Medium-Sized Web Applications and Nothing Else". If you want a broader picture, or are primarily interested in another domain, look elsewhere.

The author is clearly aiming the book at programmers who primarily program for money. Not that there's anything wrong with that, but given the author's expressed fondness for open source software (which I share) it might have been nice to acknowledge that some people also write programs for the joy of it in addition to (or in lieu of) the financial rewards.

Now that I've covered the bad, let's look at the good. The author seems to know his domain well, and he makes a good case that Java frameworks for writing web applications have gotten so baroque and tedious that they are simply miserable to use and lead to very slow development cycles. This might be just the fault of the frameworks and not the language, but the author makes a good case that specific language features (or the lack thereof) are what make Java so clumsy for writing web applications. He contrasts Java primarily with the Ruby language, and specifically with the Ruby on Rails web framework, and shows that several features of Ruby make for a much more productive programmer experience. For instance, Ruby's ability to express configuration information inside the language obviates the need for much of the XML that clutters up Java web applications. The author spends a lot of time discussing Ruby's metaprogramming capabilities and how they make it possible to write much more concise code with much less repetition. An example is a class which reads from a database and populates itself on-the-fly with methods to access specific database fields. (Small gripe: the term "metaprogramming" has a variety of semi-related meanings, all coming down to the notion of code being automatically generated instead of being written by hand, but the way that e.g. Lisp or Scheme macros or C++ templates represent metaprogramming is very different from Ruby's metaprogramming, and the author doesn't discuss that.)

The most interesting chapter by far is the chapter on continuation servers. The author gives a clear (though short) description of continuations, which is no mean feat given that they are one of the most difficult-to-explain concepts in the entire universe of programming languages. More importantly, he discusses how they turn out to be extremely useful in web servers, allowing web-based programs to be written in a much more natural and concise style than is possible without them. He uses the Smalltalk language as an example, because there is a continuation server written in Smalltalk. (Another gripe: while I'm happy to see him acknowledge that Smalltalk is a good language, I might have liked it better if he also mentioned that the Scheme dialect of Lisp also has continuations (as I mentioned above), and that there is also a web server in PLT Scheme that is also continuation-based).

The take-home message of the book is that writing small to medium-sized web apps in Java is rapidly becoming more trouble than it's worth, that more dynamic languages like Ruby have features that make it much easier, and that therefore there is a good chance that these languages will take over much of the programmer mindshare. I agree with all of these points, and think that today's Java web programmers are well advised to look at other programming languages. However, I also feel on general principles that all programmers would do well to learn another programming language every year or two, so for me this book just reinforces my pre-existing view.

On the other hand, the author mentions, but doesn't emphasize the fact that the JVM has many capabilities which far outstrip those available in Ruby or Python or indeed most other languages. He does point out that many advanced features of Java frameworks are only useful for very large scale web
applications (the domain that J2EE targets explicitly), and are unnecessary for the majority of (smaller scale) web applications. He leaves open the extremely important question of whether frameworks like Ruby on Rails will scale well to larger applications, or to smaller applications when they need to grow larger, though he seems to believe that they will (if not now, then later when the language and its implementation or implementations mature).

In summary, I think this book is a decent read with a lot of food for thought, if you can handle the irritating style, the mistakes and the omissions. This book is far from the last word on this subject (the reader should be aware that there are lots of interesting computer languages that are not even mentioned in this book, with Objective Caml and E being two obvious candidates), but it's interesting nonetheless.
16 of 19 people found the following review helpful
4.0 out of 5 stars The java developer's dilemma... Nov. 7 2005
By Eric Wuehler - Published on Amazon.com
Format:Paperback
While probably not the best analogy (on my part), the author's message seems to be similar to the book, The Innovator's Dilemma, that is on the required reading list for MBA students. The "Java Developer's" dilemma: How do you take time away from your comfort zone and what is paying the bills to focus on what isn't ready to pay the bills (the "disruptive" technology/language). I.e., there are more employers looking for Java experience than for, say, Ruby experience. So, when do you make that jump, what language should you jump to, or better yet, how do you prepare yourself to get ready to make that jump without getting left behind.

This last statement is what I took away from the first half of the book. The author gives his opinions and suggestions as to how to prepare yourself for that jump. For that, I think this book should probably be required reading for software developers in general, not just Java developers. I know a handful of ex-mainframe developers that wish they had taken time to learn something other than COBOL. :)

As noted in the other reviews, the book also discusses things such as Java's pros and cons, as well as what the characteristics of the "next big language" are likely to be. While interesting, this aspect of the book was ancillary to the underlying message I took away from the book. What I took away from the book was; when Java is replaced as the programming language of choice, are you going to be ready?

Overall a persuasive argument. If you believe Java is on the way out, this book contains your talking points. If you believe Java is king and your job is safe, this book contains the arguments you will most likely have to fend off.
13 of 15 people found the following review helpful
2.0 out of 5 stars Not up to O'Reilly standards Jan. 2 2006
By R. A. Schulman - Published on Amazon.com
Format:Paperback
Bruce Tate's Beyond Java is not up to O'Reilly standards. It's poorly organized, repetitive, and error-ridden. As of the present writing (Jan. 2, 2006), the online example code promised in the front of the book is not available on the O'Reilly web site. A long list of errata is available there, however, but it's incomplete.

Expect much frustration in trying to type in the main Ruby on Rails example and getting it to run successfully. And expect much hair-tearing at all the repetition and the author's attempt to be artsy by beginning each chapter by comparing white-water kayaking to the perils of picking a new programming language.

This would have made a good book or special journal issue at one-quarter it's present size, with better editing, and with better testing of the example code -- and deep-sixing the tedious kayak stories.
14 of 17 people found the following review helpful
2.0 out of 5 stars Not very insightful -- only touches surface Oct. 23 2005
By Shahzad Bhatti - Published on Amazon.com
Format:Paperback|Verified Purchase
I was hoping that Bruce will have more insightful comparison of upcoming languages and will compare Java's shortcomings against them. Instead, he covered only major shortcomings of Java that most people already know such as not purely object oriented, edit-compile-test cycle or how massive it has become. Though, he talks about Python, Ruby, Smalltalk, Lisp, but it is very clear from beginning that the only language that he likes is Ruby and does not provide enough details on other languages. I myself have been learning Ruby over a year and have been trying Ruby on Rails lately and I like it a lot and I agree that productivity on Ruby is much higher than Java. It's just that I was hoping to learn a bit about other new languages and how they tackle different issues especially that make domain driven modeling a bit easier similar to "Naked objects" features. I for one doing Java programming since '96 and having gone through all Java->CORBA-Servlets->EJB-Spring cycle am looking for alternatives. Certainly, Ruby comes to mind and it is going to have support for VM and AOP support in 2.0, but I am still not convinced that it is the answer. Overall, I wished the author had researched a bit more about other interesting ways people are solving these problems.
8 of 10 people found the following review helpful
4.0 out of 5 stars beyond Ruby Dec 6 2005
By Rocky - Published on Amazon.com
Format:Paperback
Bruce is a well known Java expert, most of his books are pretty good and very easy to follow.

He is always good at making difficult things easier - easier to understand and easier to implement.

In this book, he interviewed a bunch of 'language experts', most of them complained how difficult/cumbersome/awkward Java is. It's really worth reading.

I want to add more points to their opinions:

1. The current JAVA for web programming is too bad.

For say, in the popular Struts framework, you need a 'view' which is a JSP page, a 'form bean' java class just to hold all values that you need to show in the JSP page, an 'Action Form' which respond to the user actions on the page, and a 'model' class to hold the data. Finally don't forget at least 2 XML files to link them all together and specify the relation in Strut's xml config file.

To me, if we have to do web programming like this for another 10 years, that will really be a shame to all developers.

2. Don't get me wrong, Java is not a bad thing. Java is MUCH more stable and has MUCH more support than any languages.

You can almost easily find any solutions even with source code.

I wrote a lot JAVA, PERL, PHP programs. If the task is small (less than 3000 lines of scripts), scripts can do the job very easily.

The things I don't like for many script languagues are:

For PHP: no package, no scope, so you have no way to say sys.getOS(); and you can not force it to check variable declaration. Too bad if you made a typo or case mismatch.

All PHP extensions are static linked, and it has very poor support for mutithreads. We use to have 30 servers running Apache1.3+PHP4.3, each of them can not handle too many clients even the load is not high because each client will need one PHP process which is about 20M.

For Python: I really don't like __main__ __init__ stuff, they look like dirty hacks rather than well designed features.

The white space and non-C looking syntax make me really confused sometime.

Python was the slowest scripting language before.

For Ruby:

In Ruby, a + b and a +b have different meaning, I just can't get it. Ruby will give you a warning because it thinks a +b means a(+b), a is a function to call a positive numeric variable!

For Perl:

The OOP part is horrible. Actually I like Perl a lot. It's perfect for sys admins and DBAs but just so messy for developers

But PERL has something really neat:

a. PERL's getOpts and getOpts_long are the best. They are much better than Java's Jakarta Common CLI

b. PERL's SOAP::Lite is so powerful and so easy to use. 3 lines code to get you a functional SOAP server. I build a grid log searching tool using PERL CGI,SOAP::Lite and SUN Grid Engine just in one afternoon. It will take at least one week if I have to write JAVA and use AXIS.

c. PERL's 'tie' solution for Berkely-DB is the easiest on the earth. Please check the official 'SleepyCat Java Edition' then you know how difficult to write in JAVA. (I'm not saying it's poor, what I mean is that it's just way too much comlexity for day to day jobs)

Actually Groovy is a pretty good script language,

the only thing I don't like is its warnings. In PERL/PHP/PYTHON, all warnings are relevant and helpful but in Groovy, it sometimes just directly print Java complains to Groovy interpreter which has no meaning to the developer.

SUN is gonna to include Java-Script and Bean-Shell in next Java( version 6.0) and include Groovy in version 7.0.

I'd really like to see SUN's 'official' support for these languages.

There should be a Groovy framework soon and I think that might be more attractive to us.
Search Customer Reviews
Only search this product's reviews

Look for similar items by category


Feedback