Quotes About Object-oriented

PHP as an object oriented programming language should be judged by how well it does the job, not on a preconceived notion of what a scripting language should or shouldn't do.

There is no way to extend an instantiable class and add a value component while preserving the equals contract, unless you're willing to forgo the benefits of object-oriented abstraction.

Certainly not every good program is object-oriented, and not every object-oriented program is good.

Defining OO as based on the use of class hierarchies and virtual functions is also practical in that it provides some guidance as to where OO is likely to be successful.

Of course, explaining object-oriented programming as an enhanced switch is much less fancy than presenting it as a technology that helps us model the real world.

the move toward object-oriented programming, where applications could be fashioned out of small, predefined blocks of code, was a lot like building with LEGO.

Object-oriented programming is an exceptionally bad idea which could only have originated in California.

We do not want to expose the details of our data. Rather we want to express our data in abstract terms. This is not merely accomplished by using interfaces and/or getters and setters. Serious thought needs to be put into the best way to represent the data that an object contains. The worst option is to blithely add getters and setters.

Object-oriented programming is discipline imposed upon indirect transfer of control.

More precisely, the Law of Demeter says that a method f of a class C should only call the methods of these: • C • An object created by f • An object passed as an argument to f • An object held in an instance variable of C

Object-oriented programming imposes discipline on indirect transfer of control.

It's very hard to explain to people who don't program, but the object-oriented programming system made programming the Mac and iPhone so easy.

The astrolabe was a mechanical implementation of an object-oriented model of the sky.

JavaScript doesn't have a classical object-oriented model, where you create objects from classes. In fact, JavaScript doesn't have classes at all. In JavaScript, objects inherit behavior from other objects, which we call prototypal inheritance, or inheritance based on prototypes.

Design Patterns: Elements of Reusable Object-Oriented Software (Addison-Wesley Professional, 1995) by

Unlike procedural programming, which emphasizes algorithms, OOP emphasizes the data. Rather than try to fit a problem to the procedural approach of a language, OOP attempts to fit the language to the problem. The idea is to design data forms that correspond to the essential features of a problem.

Containment is the simple idea that a class contains a primitive data element or object. A lot more is written about inheritance than about containment, but that's because inheritance is more tricky and error-prone, not because it's better. Containment is the work-horse technique in object-oriented programming.

Object-Oriented Design Heuristics (1996), Arthur Riel

Just as it is a good practice to make all fields private unless they need greater visibility, it is a good practice to make all fields final unless they need to be mutable.

When designing thread-safe classes, good object-oriented techniques—encapsulation, immutability, and clear specification of invariants—are your best friends.

There will be times when good object-oriented design techniques are at odds with real-world requirements; it may be necessary in these cases to compromise the rules of good design for the sake of performance or for the sake of backward compatibility with legacy code. Sometimes abstraction and encapsulation are at odds with performance—although not nearly as often as many developers believe—but it is always a good practice first to make your code right, and then make it fast.

So Apple needed a partner, one that could make a stable operating system, preferably one that was UNIX-like and had an object-oriented application layer. There was one company that could obviously supply such software—NeXT—but it would take a while for Apple to focus on it. Apple first homed in on

One was how computers could be networked; the second was how object-oriented programming worked.

I don't predict the demise of object-oriented programming, by the way. Though I don't think it has much to offer good programmers, except in certain specialized domains, it is irresistible to large organizations. Object-oriented programming offers a sustainable way to write spaghetti code. It lets you accrete programs as a series of patches. Large organizations always tend to develop software this way, and I expect this to be as true in a hundred years as it is today.