> I have a ton of respect for Alan Kay and think he's a genius. But why does it seem like every time he talks about OO it's always painting an apocalyptic picture like we're in some kind of twilight zone alternate nightmare reality of broken patterns and models?

Because we are? Have you seen most OOP code-bases, they are a train wreck!

Could you elaborate on the “most” part? Coming from my experience on Rails over the past couple of years, I’m quite happy with what I’ve found so far.

Well, Ruby is Smalltalk with a different syntax..

I think one of the biggest issues is that languages such as Java account for large percentages of existing OOP in the wild and Java is a "kitchen sink" language with too many supported paradigms and styles.

For example, look at class attributes and methods. I'm not sure they're needed but in a language like Java the semantics often leads to wildly different programming styles within the same code base. And it's hard to enforce consistent styles using conventions.

That said, I've seen/read Kay asked directly, on more than one occasion to elaborate on his notion of a real OOP language implementation and his answers are always to coy and slippery for my taste.

JavaScript is functional and oh boy!

What does "functional" mean to you? If "OO" has a hundred different meanings, then "functional" must have at least a thousand. To me, JavaScript is definitely not functional - it lacks a notion of purity, and its meaning is the evaluation of statements, not the construction of expressions.

My point was popular languages attract masses of developers and the resulting quality of code is poor on average.

That's a good point, but it's not implied by "JavaScript is functional and oh boy!" at all.

The bar for thoughtfulness is higher than this here. Even if the J-word gets us, could we please be more informative and kind or just not say anything?

https://news.ycombinator.com/newsguidelines.html

This

> Surely our concept of objects and OOD can't be that bad

Yes, it is. Object orientation is probably the worst idea to ever have appeared in computer science, both from a philosophical and practical point of view: it is an unsound principle and it leads to disastrous engineering practices.

We will be mocked mercilessly by our descendants.

Actually, OOP is the most successful architectural style in existence.

Pretty much all the GUI software you see is OOP. Modern personal computing was invented on OO. The Web was invented on a NeXT in Objective-C on AppKit.

OOP was seen by Fred Brooks as one of the few possible technologies that come close to a "silver bullet" when he wrote NSB, and ten years later he said that this had come true.

Today, we tackle problems orders of magnitude larger and more complex than pre-OO. We have reuse at levels that were only dreamed of (and largely thought impossible) before.

etc.

Yeah, history won't be kind to OOP and OOD.

It will go down as a massive mistake that costs billions in both financial cost and just wasted human effort.

>Surely our concept of objects and OOD can't be that bad

How would you know if it were?

Because software isn't as cooperative and scalable as Alan Kay says. We are getting better at this, but probably at a painstakingly slower rate than he would like.

There are actually two languages (aside from Smalltalk) I know that are very close to Alan Kay's idea of message passing objects (as I understand it). Those are elixir and erlang.

They're usually regarded as functional languages, but they have message passing actor model at their core. It might not be the best for everything, but they definitely are very good in their niche of embarassingly parallel computation.

I would go as far as to say that the nature of most software development is similar to the state of physical infrastructure in the United States: failing because of lack of maintenance and poor practice. I strongly believe that these problems will lead to foundational collapse of our current processes and the systems that were built from them. It is equally likely that we simply keep on living with minimal modification to current way that we do things, with what I imagine will be slowed innovation.

All of the signs of general failure are starting to show: the great successes of recent computer attacks against the United States, against both public and private institutions, and the regular drum beat of data leaks.

Imagine having the level of education and knowledge that Alan Kay does and seeing a contemporary code base (I don't imagine that my work would be treated kindly by Mr. Kay)? I imagine that his view of whatever is coming is far worse than mine.