Slashdot Mirror
Effective Java
Introduction
Effective Java is a book very much in the style of Scott Myers' earlier C++ "Effective" series. The book contains 57 individual snippets of Java wisdom, broadly categorised into 10 sections including Classes and Interfaces, Exceptions, Threads and Serialisation. Scott Myers' books are classics; I was interested to see how this would compare.
The author, Joshua Bloch, has been involved in writing many industrial-strength Java libraries. His background is very much evident, in this, his first text. He consistently demonstrates the virtues of favouring libraries, clean APIs and advance design. I found the author very readable, and able to make a convincing argument, even in his more 'controversial' pieces. As with Scott Myers' books, there is a real-world, rather than purist approach taken to the language, with most of the code examples having a real-world feel to them. This is a breath of fresh air when lots of programming books tend to use more contrived examples.
The items
The author has endeavoured to keep the book accessible to less-experienced programmers throughout, while providing food for thought for the more advanced reader. For the most part this is succesful, but a small percentage of articles tend toward the simple side. Examples include 'Minimise the accessibility of classes and embers,' 'Write doc comments for all exposed API elements,' and 'Know and use the libraries.' We've all heard this advice many times and I don't feel that these add value. The vast majority however, are pitched at the right difficulty level. The selection of items is well balanced and broad, although unfortunately there are none pertinent to GUI programming.
Many of the articles are fundamentally based on known design patterns and idioms. Although a useful index to these patterns is included, I would have liked to see the virtues of design patterns summarised and demonstrated to a greater extent, perhaps in the introduction.
I was highly impressed with all code examples. Where used, they are consistently short, relevant and concise, with more verbose examples included on the website. The chosen code examples only ever assist in explaining complex concepts clearly.
The strongest area of the book for me was the section on threading. The author clearly demonstrates, for instance, how overuse of synchronised methods can lead to deadlock. He also provides food for thought on how the thread scheduler might trip us up. A section on moving from C constructs, which initially struck me as an odd category, proved very interesting and thorough. 'Replace enum constructs with classes' is a particularly interesting item, demonstrating the fragility of C enums, and indicating why the often-used replacement in Java (a bunch of public static constants) suffers from the same failings.
In conclusion
Ideally I would have liked to see some of the thinner items removed, and perhaps replaced with a section on the GUI libraries. I also liked the short prose sections, and thought the author could have spent more time setting out his stall before launching in to the items. Having said this, this is one of those rare books which could help a good programmer become an excellent one. Many of the books currently out there are aimed at either the beginner or the guru, and this book fills a gap.
I find this style of book very useful, in that I could foresee meeting the vast majority of the described situations at some point or another. So long as you aren't looking for tips to help you with your GUIs, this title is more than worth the investment.
For anyone interested, those sections in full:
- creating and destroying objects
- methods common to all objects
- classes and interfaces
- substitutes for C constructs
- methods
- general programming
- exceptions
- threads
- serialisation
You can purchase Effective Java from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
thanks for submitting a rare thing: a good slashdot book review. timothy, if you want us to pay any attention to these reviews, you need to keep the quality more like this one.
Do not talk of this Java Sanctuary. There is no such thing.
It's just not a review without the Table of Contents! :)
J. Bloch wrote the collections framework. His code is clean... I mean, really clean. Given the author's credentials, I suspect this'll stand out in the vast ocean of Java lit...
having developed many effective applications for a few years using java, i can, with confidence respond that "Effective Java" is not a contradiction. i've found that most "java haters" are those whose experience goes no further than the applet. too bad sun ever conceived of that little painful abomination.
java is like any other language, its a tool to get your job done, and contrary to popular belief, it gets it done rather nicely.
of course i don't mean to wax religious here... there's enough of that here.
sad robot making broken music
Man, I'm barely done with Douglas Dunn's
Java Rules and now I gotta read this?
Actually, I'm glad to see more book son coding effectively as opposed to the dummy approach which is a sure way to Shoot yourself in the foot when the maintenance phase rolls around.
That said, one thing copiously missing from the review is whether or not the book covers J2EE at all -- which by and far requires some guidance in the developing the most effective Java applications.
--- have you healed your church website?
Have you actually used it lately? Speed has been the biggest improvement. Sure, it used to be slow as hell, I concur, but with Java 2 (1.4) it is wicked quick. And for windows apps, it's far better than VB in at least one aspect - grids. Java has a grid object that works the way you'd want it to, resizeable, sortable, column-rearrangeable... And for data drive apps, this is a major thorn out of my side.
How are you going to keep them down on the farm once they've seen Karl Hungus?
In a Windows dominated enviorment, is there any other better alternative to what I am already using?
.NET seems to work alot better than the hideous quivering zygote that is VB6, IMHO. In particular C#.
.NET. I'd also go with Java if your IT department had any plans to change platforms in the future. .NET and company allow MS to keep a string tied to your IT decisions unless you're willing to abandon your code.
The abortion that is
Really, I would say that it depends on the environment. If the back end is Oracle or DB2, I'd probably go with Java; if it's SQL Server I'd be more inclined to go with
Intelligent Slashdot Moderations!
pb Reply or e-mail; don't vaguely moderate.
What grid object? JTable comes close to what you're talking about, but it isn't sortable by default. At any rate, you're right about the speed issue. The claim that Java is dog-slow is simply a myth.
Java probably isn't the best choice if you're coming from VB. Mainly because of how spoiled most people get after using a Microsoft IDE, and VB's is damn nice. ;)
Besides, if your skill set is based around MS products why not look into C#. I can tell you from experience that C# is a hell of a lot easier (or maybe more intuitive???) than Java. I like Java a lot, but damn is it painful to do GUI based apps. If you do decide to go the Java route take a look a the Eclipse IDE, it's not quite like using an MS IDE but it's clean and stays out of the way (cough**Borland**cough).
Sig (appended to the end of comments you post, 120 chars)
I've found ODBC-style data access in Java to be only slightly less painful than doing it in Visual C++.
I'm in a similar situation, developing and maintaining a data access application in VB6 that has reached 'critical mass', has gotten too big for it's britches, and needs to be rewritten from the ground up.
I've been doing a lot of thinking about what it will be rewritten in, and so far C# and VB.net are leading the pack. All Java has to offer me is some platform independence, which is pretty much irrelevant in my particular case, and I doubt it would be worth headaches like throwing out all the code that's written.
Anyways, this is all contingent on the dorks in marketing not selling imaginary software that I have to write 2 weeks before shipping, that I may have time to make the actual software work.
I don't need no instructions to know how to rock!!!!
Well, I believe C# is a good alternative for VB programmers. You still have the GUI design tool that you'd be accustomed to, though with all the benefits of a good object-oriented language. C# is also makes it easier to integrate pieces of a program written in multiple languages, or link to DLLs. JNI is alright, but is not as straight-forward as in C#.
I like Java a lot, though primarily for use in building web applications, not stand-alone client applications.
... is the Java 2 Performance and Idiom Guide (ISBN:0130142603), by Craig Larman and Rhett Guthrie.
Yes, yes, well said. Unfortunately not many people will PAY ME to code in Smalltalk these days! Times are tough, man, and you still have to eat. Even if I did make an effort to learn a subpop language for career purposes, I'd ultimately have to spend lots of time justifying it and marketing it to employers and customers. Ok, granted, there would probably be fewer people competing for these jobs, but that's a risk that few are willing to take.
Java and C++ are popular because they're popular. Managers are often idiots, but most are smart enough to know that when you leave they'll have to find a replacement with your skills. There are lots of Java/C++ people out there, lots of books, lots of classes. Smalltalk, not so much...
And yes, I agree, BeOS and Betamax were better, but don't forget...there's a REAL WORLD out there!
The main things I hate about Java are its verbosity and its enforced and contrived structures.
Except that verbosity and (contrived?) structures goes a long way towards keeping source maintainable. By requiring this verbosity and not to mention strongly recommending the Sun Java coding standards + Javadoc, code becomes magnitudes easier to read. Sure, it adds work and a bit of pain to the original coder/programmer, but adds substantially more ease of use for those down the line. Don't get me wrong it's still very easy to write hard-to-read-and-or-maintain code, but it's a bit easier to go the correct route.
But if that's how you get your kicks, gagged and bound with Sun sticking it to you, then so be it...
That depends on what you are referring to. You are right that Sun tends to stick it to the end user now and then and ultimately Sun can be said to be Java's worst enemy. For example, Mac OS X trying to do some amazing things with Java showing how it can be used viably, getting very little support from Sun.
After all that's said, I too still prefer C++ (even C#) over Java, but just not for the reasons mentioned.
----- "Blame the guy who doesn't speak English." -- Homer J. Simpson
This book is the best resource I've encountered for someone who knows the Java language, but wants to master its use. I can virtually guarantee that the rules and techniques covered in "Effective Java" will form the new foundation on which you will build the rest of your best practices for writing excellent Java code.
Written by the Joshua Bloch, the acknowledged expert on the subject, it is as authoritative as they come and extremely well-written. After six and a half years as a senior developer architecting and implementing algorithms and class libraries in Java, this book shocked me by summarizing much of what I knew about how to use the language effectively, while teaching me much that I did not know. It continues to top my recommended reading list for all new software developers at my company.
-dk
Man, this site is slow! Anybody would think it was made with Java .... just kidding .... I use Java all the time and I love it! It's great to see it improving all the time and being used for a whole host of different applications.
Go on, shoot some fish!
Java is slow? Maybe that's just your coding. These guys (among others) don't agree with you...
http://www.sosnoski.com/Java/Compare.htmlhttp://www.javagrande.org/jgsc98/index.html
IBM has achieved 90% the speed of C in Java. I personally use the CERN numerical libraries ... very cool, very fast. Java certainly can be fast. I've seen distributed Java beat C++ implementations hands down (that was hard to everyone to believe ... problem was C++ CORBA marshalling and the RTTI overhead in C++).
I've used Squeak, and have a background in coding Smalltalk (Digitalk, ParcPlace, IBM VA). Squeak is a great up-and-coming environment, but FAR from commercial. Can you name one commercial implementation in Squeak?
I think that lack of commercial viability makes Squeak impractical. Java, on the other hand, has scads of drop-in commercial libraries and components. This makes economic sense in business. Java also has a proven track record on the server side, and there are many, many successful commercial implementations in mission critical environments.
And NO, I don't think Java is the perfect enviroment; far from it. I've yet to see my ideal language, and I keep looking on the horizon for a dynamic functional/object/aspect language that performs and holds up in a commercial setting. In the meantime, I've got real work to do.
There are a lot of Java books out there, but this is one that will help an intermediate-to-advanced Java developer. The code examples in here are concise, clean, and hard-hitting. The layout of the book allows you to pick it up and learn something if you have 10 minutes or 2 hours.
When I was first learning Java, I often had that nagging feeling that I was making things harder on myself than need be. This book cleared up a lot of those feelings, and helped get me on the right track for some of the great tools hidden away in the Java API. The API documentation is great for showing you what members and functions are available to an engineer, but this book shows you how to use the API. The review cites the author's avocation of knowing the libraries, I would contend that this book would help you get the most out of those libraries, and increase your understanding of them.
This book has become a must-have around my office, and if you are looking to get over-the-hump and move from an intermediate to advanced java software engineer, pick up this book. It is dense with information, and will save you a ton of time and energy. What more could you ask for from a book?
Effective Java is a book very much in the style of Scott Myers' earlier C++ "Effective" series
This is about the highest praise you can give a language-specific programming guide. In his books Scott not only listed many of the ways you could get in trouble in C++, but also gave clear explanations of why they were trouble and why his recommendations were good practices. His books are top of the list I recommend to people who know the language and want to write solid fast code. If Effective Java is as good, I'll soon be adding a copy to my bookshelf.
--Jim
What does 'setting out his stall' mean? I picture somebody settling on to the toilet and opening the newspaper, but in the context I don't think that's what you meant.
Thank you, a good review of an excellent book. I have maybe 10 java books, most of them from O'Reilly and none have been as beneficial to my development in Java as this one.
The code and the text are both very clear and concise, and you can read the book cover to cover, coming back later to study each advice more in depth.
I think you can get it from reading between the lines in the review, but just to make it clear to any curious beginner, this is not the first book you should buy if you are just starting to learn java. Use
The Java Tutorial instead, and maybe
Learning Java.
Being bitter is drinking poison and hoping someone else will die
What? Did I forget to include emoticons or tags? Did I not make the references to "Logan's Run" explicit enough? Sheesh. Flamebait.
This is a fantastic book, and anybody's who's serious about writing good Java code should study it carefully. It's one of the best-written books -- may the best -- on the practical details of programming that I've ever encountered, and the advice is gold. The section on correctly implementing equals() and hashCode() alone is almost worth the price of the book.
The reviewer complains about some of the thinner or more "obvious" items, but I disagree. Heaven only knows how many times I've wished that really good and experienced programmers follow what seems the obvious maxim: "Minimise the accessibility of classes and members."
It's true that "Know and use the libraries" seems rather obvious and vague advice, but Bloch's exposition drives home the fact that you may not follow this advice as well as you think. As always, his examples are excellent: he shows how an innocuous-seeming abuse of java.util.Random creates serious problems, and how proper use of the libraries fixes the problem. How often do you write a loop to print the contents of an array? I never realized until Bloch pointed it out that System.out.println(Arrays.asList(array)) accomplishes the same thing much more simply.
If you're a Java programmer, get this book. If you're a technical author, aspire to it.
Let me guess - you don't program much, do you?
Java is one of the most productive languages in the world. End of story.
You could go with Delphi. Anecdotal evidence suggests that many VB programmers are switching to Delphi rather than to VB.Net.
Visually, there are lots of similarities with VB, but with more power. You can go under the hood and get as low-level as you want, short of device drivers (where at least a small part must be written in C/C++).
As a bonus, data-aware controls actually work! (even MS recommends not using them in production VB code.)
There is a version (C++ Builder) that uses C++ instead of Pascal as the basic language, and another package, Kylix, that can compile Delphi/C++B source code to run on Linux.
Borland also hosts a fantastic developer community (especially newsgroups), and most components, even commercial ones, have source available. Look at Torry's for thousands of components/tools/apps.
Many important Java techniques and idioms are described so well in this book that I have been known to insert comments to the effect of:
(or some such) into my code. Most of the author's items should be as engrained in the mind of a Java developer as terms like 'singleton' and 'event listener'.
whenYouCan(keepReferencingYourObjects)->LikeThi
Actually, it should be:
whenYouCan(keepReferencingYourObjects).LikeThis
remember, no pointers... *wink, wink*
Anyways, I have yet to see anything that bad (I know you were making a point), nor have I seen anything similar that can't be fitted within 80 columns on 2 lines. You can't seriously tell me you have never seen a C/C++ line that long. You can always write horrible code no matter the language, blaming it on the language itself is just an excuse.
What are your reasons for preferring C++ (or even C#) over Java? Speed, standards-compliance, readability, lower memory usage, saner language constructs, not controlled by Sun?
Speed - used to be, IBM is doing some amazing things with their JIT compilers. I think someone else mentioned they were getting 90% of native code. So this is no longer an issue for me. I've even writing some fairly advanced 3D apps using GL4Java.
Standards-compliance - well... not sure what to say here. There's not ASCI Java if that's what you mean. Never been much of an issue for me.
Readability - as I have been arguing above, I prefer Java's... just me I guess?
Lower Memory Usage - For sure! Java's memory footprint is horrible. Price you pay for a virtual machine. I do hate this.
Saner Language Constructs - see Readability.
Not Controlled By Sun - someone has to control it, I'd say they are doing a decent job of maintaining the API. They also seem to do a fine job of listening to the needs of the users. I think sun does a fine job with the API itself, they need to improve their application of it (Sun's JVM pretty bad, etc).
My main reasons for preferring C++...
- lower level, like the control I think.
- Sun's Swing and AWT API's suck IMHO.
- Java is very large API, I get a bit overwhealmed at times.
----- "Blame the guy who doesn't speak English." -- Homer J. Simpson
Best of all, it's not 3 feet think like Effective Java Unleashed or The Effective Java Bible would be. You get lots of info with minimal fluff.
Washington, DC: It's like Hollywood for ugly people.
Shouldn't that be :
?Smart guys, those parser builders. Not to mention that if *that* is your problem, you can pay a little performance penalty and give names to all those intermediate objects.
"Oh, I hope he doesn't give us halyatchkies," said Heinrich.
Chapters
The authors include Hans Bergsten, William Crawford, Dave Czarnecki, Andy Deitsch, Robert Eckstein, William Grosso, Jason Hunter, Brett McLaughlin, Sasha, Nikolic, J. Steven Perry, George Reese, and Jack Shirazi.
This not a bad book. For $34(USD), there are some good learnings. This is one to have on the shelf.
Of course there is the right tool for every job, and Java, while being correct for some tasks, is not the best tool for others. You, on the other hand, can rest assured that no matter what job you are doing, you will always be a tool.
"Clicky-clicky-drag" does not mean that you're not developing apps the proper way. A key idea (ideal?) in software engineering is code reuse and rapid development. If you have to write 34 methods to accomplish a text box for every app you write, then you're just wasting time. Sure C is great for mathematically intense stuff like DSP, and it's great fun for memory mis-management, but I wouldn't use it for a frontend. Use a good platform independent front-ending language, like java, to provide an interface to your powerful computational engine written in C or Lisp or Perl.
How are you going to keep them down on the farm once they've seen Karl Hungus?
When this came out in 2001, James Gosling showed a copy of it at his keynote at JavaOne. They sold out every copy they had at the show, and the Effective Java talk later that day/week, was so packed you couldn't even get it. Great book.
I rarely find a tech book that offers more than a few examples I ear-mark. This book however has me re-reading it from time to time. The lessons picked up take time to sink in, and IMO no one can truly pick up all of the lessons on one read through.
You might be interested in reading this information at the VB developer center.
mbbac
I've been required to use Java non-stop from late 1995 until quite recently for school, internships, and then for my career. I've used every version of Java, and every API and just about every class available in the SDK. I've written applets, mathematical programs, games, medical database apps for the department of defense, class projects, enterprise-level call center applications, and just about anything else you could possibly conceive.
I've found in my experience that Java is good when it's highly specialized and kept very small and simple (yes, Java is good for APPLETS!). For enterprise applications, it _sucks_.
It's not that the language itself is bad (although it certainly has some gaping holes). It has more to do with the poor (buggy) implementation of the APIs and the real-time interpretation. Java isn't nearly as portable as they would have you believe (writing a 100-line applet and then running it on two different web browsers will tell you that.) Additionally, in my opinion, Java would have been much more useful if had been designed as a compiled (not interpreted) language.
In my current job, I use a lot more C++. I like it. It does what I tell it to do, and I don't have to second-guess the tools every time there's a problem.
...just my 2 gil.
Decent review of an excellent book.
I read books like other people eat hot dinners, and when I recommend Java books in work I only recommend this one. (I tend to find that a surprisingly number of coders only read one or two tech books a year anyway). "Effective java" is very well written; it's nice and short without sacrificing any exposition of the hairer parts of the language.
And as another poster has said, at work it's often sufficient to say in a review, "HashCode as per Bloch please"
It's nice to see a book review that actually reviews the book, rather than just regurgitating the table of contents.
"I don't know half of you half as well as I should like, and I like less than half of you half as well as you deserve."
"It's a tool to get your job done"
Which is a very sensible sentiment. The problem is that, because Sun has spent millions of dollars marketing it, management now thinks that it is the only tool to get the job done, when there are many other fine tools, such as C, Tcl, Python, etc... that each have good features.
That's what I find frustrating about Java. That and the fact that I like free software, and the Java comunity doesn't seem to have the strongest of relationships with those ideals.
http://www.welton.it/davidw/
Four sample chapters from the ten in the book are available in PDF format at the books website.
whenYouCan(keepReferencingYourObjects)->LikeThi
This code is a horrible violation of the
Law of Demeter. If you're doing this, formatting is not your biggest concern.
There is something about the idea of code examples being "hard-hitting" that made me laugh out loud.
Random is the New Order.
Ok, maybe you should view what I posted, and re-read the links.
IBM makes claims to Java at 90% speed of C++ in their numerical benchmarks. JavaGrande includes a number of well-respected organizations doing intensive computation, including GRID work. The tests quoted show a wide variety of performance, and you picked on file I/O; yes, one of the worst aspects in those tests. However, note that these are OLD JVM tests, not the significantly improved I/O found in JDK 1.4. (I don't have stats handy but have seen and experienced the claims of improved performance).
Java as an interpreted, cross-platform language will always be at a disadvantage to C++ in terms of raw speed. The again, many equate C++ as "Object Assembly" in the OOP world. That has it's own disadvantages.
Everything depends on how the language gets used. I have written many distributed C++ infrastructures and applications, and find Java a much welcome alternative. In many distributed scenarios it has proven faster, to the surprise of many seasoned collegues. I couldn't even imagine the jirations required to do an equivalent of JINI in C++.
So, why is it that most financial institutions have dropped C++ in favor of Java for server applications? It must suck something fierce, eh?
So sorry. My weird sense of humour strikes again.
Don't learn Java. Learn OOP, and implement what you learn, as you learn, in Java. That is the best advice no one ever gave me. When you learn OOP, it doesn't matter what Java-like language you learn, as the real skill will be portable to other languages, like C#, SmallTalk, Python and Ruby. Let me explain.
I recently decided to go into the field of programming, and probably don't have 1/10th your development experience. However, my research skills are equal to anyone that I know, and they've certainly helped me in getting a grasp on the fundamentals of software engineering (or problem solving as I've learned to call it).
I chose Java because of its touted strengths, and because I wasn't sure of my target platform yet. I soon understood that as an introductory language, it has some conceptual hurdles that may get in the way when first learning to program. After a while, I began to understand the basics of programming by supplementing my self-study with older languages like BASIC. Essentially, diving straight into Java without first learning the standard structures of programming (sequence, selection, and repetition) was a handicap. However, for someone who already knows Visual Basic, such as yourself, the biggest hurdle will be the concepts of Object Oriented Programming.
If you think you "know" Object Oriented Programming but have only implemented it in VB, then I would suggest that you may not know everything that you need to program in OOP properly. There are plenty of Java programmers out there, but looking at some of their code, I see a definite lack of understanding in how to implement OOP. I see procedural programming techniques being applied to a language that will allow for it, but the developers lose the real advantages of using OOP.
I would recommend that you get a "beginners" book on Java (John Smiley is an excellent resource with his Learn To Program Java) to become familiar with the mechanics. If you prefer, you can try a Java in 21 Days/24 Hours type book. It doesn't matter, because if you follow my advice, you will actually learn to program OOP which is by far the largest hurdle, not syntax/grammar/classes. The most beneficial book I've found on the subject is from a master on the subject:
Sams Teach Yourself Object Oriented Programming in 21 Days
by Anthony Sintes
ISBN: 0672321092
This book will not only teach you how to program OOP, it will teach you to do it the right way. This is done by showing you how not to program OOP, and immediately showing you an alternative.
The author has some serious credentials: "Tony Sintes has worked with Object-Oriented Technologies since 1995. In that time, Tony has been part of many object-oriented development efforts. Currently, he works for BroadVision where his main responsibility as team mentor, building the skills of less-experienced developers. He brings his years of experience and ability to teach to different projects in order to guarantee their success.
Tony Sintes has written for JavaWorld, Dr. Dobb's Journal, LinuxWorld, JavaOne Today, and Silicon Prairie, where he produced a highly-regarded monthly column on Object-Oriented Programming. Tony currently writes JavaWorld's monthly Q&A column."
About the book: "Sams Teach Yourself Object Oriented Programming in 21 Days differs from other OOP books in two main ways. Many classic OOP books are designed for software engineers and teach at an academic level. Sams Teach Yourself Object Oriented Programming in 21 Days presents accessible, user-friendly lessons designed with the beginning programmer in mind. Other OOP books work to present both OOP and to teach a programming language (for example: Object-Oriented Programming in C++). Although Sams Teach Yourself Object Oriented Programming in 21 Days uses Java to present the examples, the book is designed to present concepts that apply to any OOP environment."
Days 1-7 cover the core OOP concepts with every other chapter covering the implementation of the concepts in the previous chapter and a boatload of do's and don'ts. For instance, in Chapter 2 you learn about Encapsulation theory (more importantly, what NOT to do). Chapter 3 you write code implementing Encapsulation...and so on.
Days 8-14 covers how to apply the OOP you've learned using design patterns like MVC.
Days 15-21 take the things you learned in the past 14 days, and make a GUI-based application. You apply the MVC pattern in making the app. Very cool.
It's awfully funny that your example, which was supposed to illustrate something bad about Java, is actually C++, and not legal Java. Even more ironic, the Java equivalent would be several characters shorter.
Nah. Server side Java is the thing these days. With a good JIT Compiler, your steady state performance is going to be very good.
catch (ModDownException mde) {post.modUp("Interesting")}
...that Effective Java talks about by using a static code analyzer. Like this one:
http://pmd.sf.net/
PMD will find places where you've used concrete collections rather than interfaces, left unused code lying around, etc., etc.
Tom
The Army reading list
Effective Java is the best second book for learning to program well in Java. The best first book is Thinking in Java by Bruce Eckel, which is just out in its third edition.
You forgot to mention that most of Bruce Eckel's books are available online in a variety of formats, for free.
I've found in my experience that Java is good when it's highly specialized and kept very small and simple (yes, Java is good for APPLETS!). For enterprise applications, it _sucks_.
Interesting observation...
Why don't you give us some specific examples to back up that sweeping statement?
Push the button Max!!!!
GridLayout or GridBagLayout layout managers for positioning components in the window.
I have always worked on the principle of one new thing per project wherever possible. New languages are a no-no, so when I speced out projects, we stuck with languages where there was a good level of in-house knowledge - and delivered on time. Java is mainstream now so it remains a good choice even though there are OO languages that may be better. It is well supported and comes with a good collection of objects.
See my journal, I write things there
In two words, dynamic compilation and inlining. You can do a lot more with dynamic information and dynamic performance profile. Being able to inline 50-100 nested calls in a hot spot may give you something the most sophisticated static compiler will never dream of.
(F.e. you can eliminate a virtual method call just because you dynamically know what method you are actually calling; you can inline methods from system and third party classes, etc.). Just don't forget to add -server to your java run.
I'm trying to write a Java chess app just for fun to see if I can do it and if Java is actually a limiting factor in the project. So far I'm very impressed with the Java performance. Definititely no show-stopper even in such a performance-critical field.
you seem to be under the illusion that java exists only for web pages. you are wrong. Most java is not contained in web pages.
-------------------------
A person of moderate zeal
Which APIs? Which bugs? Nothing is bug free. Also, your comment about "real time interpretation" is off base, see below.
Java isn't nearly as portable as they would have you believe (writing a 100-line applet and then running it on two different web browsers will tell you that.)
Applets apply to Java portability how again? Are you under the impression that some significant amount of Java development today relates to applets? Answer: not really. Further, if you use a decent JRE in both browsers you'll find you have no applet portability problems either.
Additionally, in my opinion, Java would have been much more useful if had been designed as a compiled (not interpreted) language.
Now you are exhibiting true ignorance for the world to see. There are many traditional, ahead of time, Java compilers. gcj, TowerJ and Jet come to mind. Look back at the recent article on x86 Linux numerics. Check out the linked article from that post - note gcj is only 9% slower than g++. Supposedly gcj 3.3 and 3.4 both improve gcj speed substantially over the 3.2 compiler used in that article...one guesses the more mature g++ will see less speedup.
In short, your reasons for liking C++ over Java don't hold water except for verbosity. ;-)
(BTW, I'll give you a strong reason for disliking C++ - you can't turn on bounds checking in STL arrays using operator[] without hacking STL. Ugly.)
Galileo: "The Earth revolves around the Sun!"
Score: -1 100% Flamebait
I know two Java books that are definitely worth their money:
- Effective Java
and
- Java Platform Performance by Steve Wilson and Jeff Kesselman
Of the second book there is a HTML version available at this link
Signature deleted by lameness filter.
AWT/Swing are still too slow. Even with the latest release.
For reasonable GUI performance SWT is the way to go. The object model approximates AWT's so there's not a huge learning curve if you want to experiment.
Can you name one commercial implementation in Squeak?
Good point. However how many commericial applications are written in Java? I am not talking about custom client/server apps or installer programs but popular shrink wrap applications that are written in Java? Just curious as I never seem to encounter any and often wonder why not - given the Java advantage of cross-plateform capability.
If you're interested, you can get a free subscription to the print edition of Software Development Magazine. It's one of the few high quality freebees (and no, I am not affiliated with them). Also, as Scott Myers got mentioned here a few times: He writes for SD Magazine once in a while.
Under capitalism man exploits man. Under communism it's the other way around.
This is the best java book I have read. I swear I already knew 80% of what is in the book but I had forgotten half.
But the most useful thing about the book is that you can quote it to people. It has been a useful tool for applying to the Open Source mailing list I have to participate in.
And if you are writing an API in Java you need this book shipped to you overnight delivery. You can thank me later.
Read Epic the first RPG novel.
I'm not a big fan of Java, but I was impressed by everything that has been said here about how much Java has matured, so I figured I'd put it to the test.
I dug up some old benchmarks (the BYTEmarks, which includes a jBYTEmark, normalized to that same P90) that I can use to fairly compare Java and C performance.
I've got a 1.2Ghz Duron, and the C version of the BYTEmarks seems to reflect this accurately--with scores of 26.6 Integer and 21.4 FP, with a P90 being 1.00.
I'm comparing this against two separate Java implementations--Sun's JVM for Linux, and gcj (I also tried out a program that translates Java bytecodes to C, but the resultant executable didn't perform correctly). Here's a table of results:
C Bytemark: INT: 26.6 FP: 21.4
SUN (--server) INT: 4.21 FP: 1.80
GCJ INT: 3.63 FP: 1.71
SUN (Default) INT: 2.18 FP: 2.14
Now, I'm not surprised that the C version ran so fast, but I am surprised the the Java benchmarks did so badly, considering that both benchmarks were normalized to an index of 1.0 for the same Pentium 90! Maybe I got a bad copy of the jBytemarks--it was hard to find a copy at all--but it looks pretty legit.
Do any of you Java people have some amazing tips for me? I did use all the optimization flags I could find. Or is this typical performance for Java, making a 1.2Ghz Duron run as slow as a P200 or a K6/300?
pb Reply or e-mail; don't vaguely moderate.
After doing a bit more research about JVMs, I installed IBM's JVM, which outperforms both GCJ and Sun here:
IBM INT: 5.8 FP: 6.4
These results still aren't as good as I'd hoped, but it does show that all of the JVMs aren't up to par yet, and therefore should be careful in choosing one!
pb Reply or e-mail; don't vaguely moderate.
You, on the other hand, can rest assured that no matter what job you are doing, you will always be a tool.
Mind if I borrow that?
I didn't realize that there were so many Java fan(atics) out there. I do realize it's importance to the computer industry, and especially the acedemic industry, but there is a lot of bloat to the language. Java has become a wishlist of functions. Great for learning and teaching OOP, but as it's been abstracted too far (in my opinion) it has lost a little bit of flexibility (and a lot of its speed). Personally, I don't care about overloading methods, total abstratcion, or write once debug everywhere capabilities. Garbage collection is nice though, as well as the additional security Java has to offer, but as far as it being the last word everywhere, just ask Corel.
Your suggestion to Use a good platform independent front-ending language, like java, to provide an interface to your powerful computational engine written in C or Lisp or Perl does make sense though, and you didn't have to come across as a zealot.
I'm burning Karma to reduce my heating bills...
You think that I'm crazy, you should see this guy!
A portable text editor w/ standard features would probably only need 200 lines or so since most of the functionality is provieded from the API, the power of OOP.
...until my employer made me work with Java visionary and author Patrick Naughton. Now I don't want anything to do with it.
Best Buy can have you arrested
I am an infrequent Java programmer, but I found this book extremely useful when thinking about design in other languages. Much of the advice about how to fashion reusable libraries, how to think of the users of your class as potential wrong-doers is extremely useful.
It's all very well in practice, but it will never work in theory.
Firstly, a Java application written for Java 1.0 will still compile and run with Java 1.4. When the C++ standard (or the subset of the standard that any given compiler actually implements) changes people do not have any such guarantee.
Secondly, I'd be interested in knowing exactly what 'powerful and useful' functionality Sun is holding back?
This is a great book for those who know some about Java, and want to know more.
:-)
Also, if you ever get a chance to see Joshua speak, go for it! He's a really engaging speaker, much better than the rest of us nerds
I remember the AWT and then, especially, Swing being extremely buggy. Trying to get a combobox to display correctly when you put it at the bottom of a window is one of the many problems I can remember right now. I understand that the APIs are still "new" (relative to the STL?) and constantly under development, but that makes using Java a poor management decision.
Applets apply to Java portability how again?
The Java platform is ported both to operating systems and to browsers. Using applets as an example of the poor portability of Java bytecode across different Java platform implementations is a perfectly good example of the over-hyped "portability" of Java. "A lot of people don't use Java applets" is not a good rebuttal.
Now you are exhibiting true ignorance for the world to see.
You should know that when you attack the person on the other side of the discussion, you're making it easier for the more intelligent readers to dismiss your arguments. As I said (and as you quoted), Java was designed to be an interpreted language. Yes, there are "real" Java compilers out there, and they're getting pretty good. I'm excited for what the future has in store for the maturity of free Java platform implementations. But the Java compilers available have never been good enough for management to say "let's use gcj instead of Sun's JVM".
Notice I never said that "Java is slow", although you spend an entire paragraph trying to convince me otherwise. The dynamic recompilation (JIT) that is available in most Java compilers is certainly a good thing, and compiled java is even better. But memory consumption, API compatibility (!), and yes, even speed, are things that need to be considered in a language that's going to be the foundation of a substantially large application.
I'll give you a strong reason for disliking C++ - you can't turn on bounds checking in STL arrays using operator[] without hacking STL.
Are you saying that C++ is a bad language because the STL doesn't do bounds checking on arrays?? I can personally think of several reasons for disliking C++, but that's never been one of them.
...just my 2 gil.
So that is why my J2EE App Server only works about once a week. It is when you turn it on.
AWT was never slow. Swing is now quite fast with the 1.4 release. SWT is cool too, but harder to extend the functionality of compared to Swing.
If I were in your shoes I would go with VB.NET. With .NET VB finally became a real language. I still don't like using it, but I have to give it some grudging respect.
Under capitalism man exploits man. Under communism it's the other way around.