News for hackers. Stuff that matters.
Re:Why Racket? Why Lisp? (2014) by gmfawcett on Wednesday September 14, 2022 @03:30PM (#32842129)
We should stop invoking Alan Kay's ancient opinion in OOP discussions. I suggest we rebrand his flavour of programming as "message oriented programming" (MOP), thank it for its continuing contributions to the field, and recognize that contemporary OOP is a valid but different solution space.
Re:Why Racket? Why Lisp? (2014) by samatman on Wednesday September 14, 2022 @04:12PM (#32842714)
Rather, we should insist on calling object oriented programming what it is, and come up with an acronym for the poor imitations.

How about Class-Reified Abstract Programming? If the shoe fits...

Re:Why Racket? Why Lisp? (2014) by gmfawcett on Wednesday September 14, 2022 @05:41PM (#32843773)
Modern OOP isn't a poor imitation of anything, it's a distinct approach with its own merits. The No True OOP meme is old and tired, and frankly pointless.
Re:Why Racket? Why Lisp? (2014) by cutler on Thursday September 15, 2022 @01:41AM (#32847534)
Agreed. Smalltalk is Smalltalk and corporate OOP(Java/C#) is what it is. Neither is superior or more pure.
Re:Why Racket? Why Lisp? (2014) by pie_flavor on Thursday September 15, 2022 @03:37AM (#32848462)
Smalltalk came after Simula, which created the "poor imitation" you refer to. The reason you remember Kay instead of Simula is because Simula's ideas actually worked and so instantly got adopted by too many languages to care where it came from.
Re:Why Racket? Why Lisp? (2014) by eyelidlessness on Wednesday September 14, 2022 @09:31PM (#32845894)
It’s imperative programming with dots/infix sigils and either a little or a lot of ceremony.
Re:Why Racket? Why Lisp? (2014) by Existenceblinks on Wednesday September 14, 2022 @04:52PM (#32843188)
In this era, DeepClass is a kool name.
Re:Why Racket? Why Lisp? (2014) by danielam on Wednesday September 14, 2022 @10:39PM (#32846330)
Too much mutation leads to deep state.
Re:Why Racket? Why Lisp? (2014) by felideon on Wednesday September 14, 2022 @03:40PM (#32842297)
Clarity is certainly important, in which case I could have said “OOP should have been...”

Except: Smalltalk still lives (Squeak) and Erlang takes messaging to the extreme.

Re:Why Racket? Why Lisp? (2014) by Twisol on Wednesday September 14, 2022 @03:42PM (#32842323)
I've not used Erlang much, really, but it seems like a really nice fusion of messaging across agents and immutable state within agents. Elixir has long been on my list of languages to properly pick up...
Re:Why Racket? Why Lisp? (2014) by goatlover on Wednesday September 14, 2022 @04:33PM (#32842978)
Also since Simula proceeded Smalltalk, and C++ is inspired by Simula, and Java by C++.
Re:Why Racket? Why Lisp? (2014) by pjmlp on Thursday September 15, 2022 @01:52AM (#32847622)
I always take a point to address the "Java coding in C++", as what actually happened was Java adopting what was the C++ approach to library development before Oak turned into Java.
Re:Why Racket? Why Lisp? (2014) by renox on Thursday September 15, 2022 @12:19PM (#32854287)
That's funny but for me Erlang is much more MOP than Smalltalk
Re:Why Racket? Why Lisp? (2014) by gmfawcett on Thursday September 15, 2022 @12:37PM (#32854589)
Sure. Reading the qualifications that Kay makes at the end of his quote (above), he leaves room for Erlang to be MOP. I suspect that he just wasn't familiar with the language.