News for hackers. Stuff that matters.
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.