Recently, I was trying to convince a few of my readers that a better understanding of an object in OOP would help us solve many problems in existing pseudo-object-oriented languages. Then, suddenly, the question came up: "What problems?" I was puzzled. I thought it was obvious that the vast majority of modern software written in modern OO languages is unmaintainable and simply a mess. So I Googled a bit, and this is what I found (in chronological order).
The list of quotes is sorted in chronological order, with the oldest on the top:
Edsger W. Dijkstra (1989)
"TUG LINES", Issue 32, August 1989
"Object oriented programs are offered as alternatives to correct ones" and "Object-oriented programming is an exceptionally bad idea which could only have originated in California."
Alan Kay (1997)
The Computer Revolution hasn't happened yet
"I invented the term object-oriented, and I can tell you I did not have C++ in mind." and "Java and C++ make you think that the new ideas are like the old ones. Java is the most distressing thing to happen to computing since MS-DOS." (proof)
Richard Mansfield (2005)
Has OOP Failed?
"With OOP-inflected programming languages, computer software becomes more verbose, less readable, less descriptive, and harder to modify and maintain."
Eric Raymond (2005)
The Art of UNIX Programming
"The OO design concept initially proved valuable in the design of graphics systems, graphical user interfaces, and certain kinds of simulation. To the surprise and gradual disillusionment of many, it has proven difficult to demonstrate significant benefits of OO outside those areas."
Linus Torvalds (2007)
"C++ is a horrible language. ... C++ leads to really, really bad design choices. ... In other words, the only way to do good, efficient, and system-level and portable C++ ends up to limit yourself to all the things that are basically available in C. And limiting your project to C means that people don't screw that up, and also means that you get a lot of programmers that do actually understand low-level issues and don't screw things up with any idiotic 'object model' crap."
Oscar Nierstrasz (2010)
Ten Things I Hate About Object-Oriented Programming
"OOP is about taming complexity through modeling, but we have not mastered this yet, possibly because we have difficulty distinguishing real and accidental complexity."
Rich Hickey (2010)
SE Radio, Episode 158
"I think that large objected-oriented programs struggle with increasing complexity as you build this large object graph of mutable objects. You know, trying to understand and keep in your mind what will happen when you call a method and what will the side effects be."
Eric Allman (2011)
Programming Isn't Fun Any More
"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. The methodology looks clean and elegant at first, but when you actually get into real programs they rapidly turn into horrid messes."
Joe Armstrong (2011)
Why OO Sucks
"Objects bind functions and data structures together in indivisible units. I think this is a fundamental error since functions and data structures belong in totally different worlds."
Rob Pike (2012)
"Object-oriented programming, whose essence is nothing more than programming using data with associated behaviors, is a powerful idea. It truly is. But it's not always the best idea. ... Sometimes data is just data and functions are just functions."
John Barker (2013)
All evidence points to OOP being bullshit
"What OOP introduces are abstractions that attempt to improve code sharing and security. In many ways, it is still essentially procedural code."
Lawrence Krubner (2014)
Object Oriented Programming is an expensive disaster which must end
"We now know that OOP is an experiment that failed. It is time to move on. It is time that we, as a community, admit that this idea has failed us, and we must give up on it."
Asaf Shelly (2015)
Flaws of Object Oriented Modeling
"Reading an object oriented code you can't see the big picture and it is often impossible to review all the small functions that call the one function that you modified."
If you have something to add to this list, please post a comment below.