Java in Practice – Buch gebraucht kaufen

0201360659

(ISBN-13: 9780201360653)

leichte Gebrauchsspuren

209

463 g

Hardcover/gebunden

Englisch

Zustand siehe Bild. Zusätzlich: Ecken und Kanten kaum bestoßen. Seiten und Buchschnitt altersbedingt kaum abgedunkelt. Dritte Seite Namenseintrag.


Introduction

The design of the Java platform reflects a shift in priorities in both computer languages and systems design. This shift has brought about changes that have had very subtle yet profound effects as the use of the Java platform has steadily matured.
One key change has been that Java has reversed the trend of object-oriented (OO) languages becoming increasingly complex. It is Java's relative simplicity that makes it so clear at expressing the solutions to programming problems, making it a wonderful language both to learn and to teach. This simplicity allows us to Lift our gaze from the world of language constructs, to the wider and muck richer world of object-oriented design and language idioms.
What we have tried to do in this book is to set down some of our Java experience in the manner of a discussion; which is really about how to solve programming problems with the Java platform, using a set of design principles.
It is a discussion about how the design is affected by the use of Java and about how certain patterns that appear commonly in software can be reflected into the Java world as idioms. Occasionally we have distilled our experience into Java rules, design principles, or tips.
Java rules simply must be adhered to. We do not define them, they are normally defined in the Java Language Specification, but we introduce them when they become salient to the discussion. We have assumed that the more obvious Java rules are known, leaving us the more esoteric ones that form the "hard walls" that mark out the edges of the design space in which we are working.
The design principles outline ideas that are generally going to help you to make better Java software across the board. They are not always going to apply but we have found them extremely useful in a number of cases.
You might choose to use the tips to guide your thinking and approach to solutions. If you find yourself in a corner, but it has the shape of a situation that we have already described, it might be useful to apply a tip.
As with all things, please keep in mind that blindly learning and applying these rules, or copying the code examples, is really not what this book is all about. What is most important is following and appreciating the arguments that support the decisions that we make in the development of this discussion.
You may not even agree with some of the solutions that we propose, but we hope that you can see the point in most. The key is to see the process of the design and stated objectives of the system being fulfilled via the use of Java. When you come to apply these ideas in your own work, in almost every case, there will be subtle forces at work that we cannot consider in general forms and so these ideas and principles may apply in slightly different ways.
For us it is this constant subtle variation that is the real joy of developing software in an iterative manner. It is the opportunity to mold a design, so that it slowly becomes a better and better "fit" for the problem that we are given, that is illuminating and the source of a never-ending set of new ideas.
In keeping with the philosophy of simplicity, this book is divided into two parts. The first three chapters introduce the three fundamentals — the "lingua franca" — of object-oriented design in the form of encapsulation, inheritance, and polymorphism.
Only when we understand these key concepts can we begin to work productively with the idioms that we present over the course of the remainder of the book. You will find that these basic ideas are mapped and remapped into various forms as we discuss the solutions to a very varied set of programming problems in the forms of "real¬world" examples and occasionally "real bizarre" examples.
Recently it has become popular to look upon the Java libraries in the same way that hardware designers look upon the chips that they use to produce a computer design. Hence the Java libraries become the packages that we must "wire" together to produce our new software systems. This is an incredibly powerful model that encourages global reuse and commoditization of these software components.
So given this model and its benefits, how does this book stand? In essence it is a set of suggestions about how we wire these components together to create new products and software solutions. What is really important is not the chips, or even the wire, it is the how and the why of the design.
Enjoy

1999

BN8733