Niklaus Wirth Quotes

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

Another trick in software is to avoid rewriting the software by using a piece that's already been written, so called component approach which the latest term for this in the most advanced form is what's called Object Oriented Programming.

Object-oriented design is the roman numerals of computing.

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.

Ruby inherited the Perl philosophy of having more than one way to do the same thing. I inherited that philosophy from Larry Wall, who is my hero actually. I want to make Ruby users free. I want to give them the freedom to choose.

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

I won't sit here and say an Open Source project will do things faster than a closed source, but one of the reasons why is that it sits on a whole lot of things that came before it.

Lisp isn't a language, it's a building material.

Object-oriented programming as it emerged in Simula 67 allows software structure to be based on real-world structures, and gives programmers a powerful way to simplify the design and construction of complex programs.

I made up the term "object-oriented," and I can tell you I did not have C++ in mind.

I used to be enamored of object-oriented programming. I'm now finding myself leaning toward believing that it is a plot designed to destroy joy.

You can prematurely optimize maintainability, flexibility, security, and robustness just like you can performance.

Adding functionality is not just a matter of adding code.

I don't like stuff that can only go into one set; I want stuff that can be applied across sets. It's a more real Lego building experience. And, of course, it's the same from a manufacturing point of view. I want elements that are universal; that gives me the best economics and best utilisation of the mould.

Our technology is very scalable. Our software can accommodate enormous numbers of clients. It's a marvelous opportunity. We'll keep developing products.

The software industry has to become better in componentization. That's a clear focus for most of the software companies. How components look, how they are maintained, the ability to maintain them separately.

We've broken the code base into logical chunks, called modules, and the foundation staff delegate authority for the modules to people with the most expertise.

The key virtue of orbital assembly is that it eliminates the tight connection between the size of the expedition and the size of the rockets used to launch it.

No one wants one language. There are applications when it's appropriate to write something in C rather than in Java. If you want to write something where performance is much more important than extensibility, then you might want to choose C rather than Java.

If you're talking about Java in particular, Python is about the best fit you can get amongst all the other languages. Yet the funny thing is, from a language point of view, JavaScript has a lot in common with Python, but it is sort of a restricted subset.

In my daily work, I work on very large, complex, distributed systems built out of many Python modules and packages. The focus is very similar to what you find, for example, in Java and, in general, in systems programming languages.

A programming language is low level when its programs require attention to the irrelevant.

Nevertheless, I consider OOP as an aspect of programming in the large; that is, as an aspect that logically follows programming in the small and requires sound knowledge of procedural programming.

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.

From the point of view of the people who are using the platform, one of the most valuable things about Java is the consistency, the interoperability.