who called it object oriented programming and not class struggle
elle mundy
who called it object oriented programming and not class struggle 63 comments
elle mundy
@teajaygrey he also regretted naming it that, wishing he’d focused more on the point, which was the messaging between objects
Óscar Morales Vivó
@teajaygrey @exchgr I'd expect Mr. Kay to mean what he did, in other words SmallTalk. But of course everyone went a different direction because performance (and then somehow we all ended up running JS anyway).
Óscar Morales Vivó
@teajaygrey @exchgr Goes to show you can't actually create a powerful, successful programming language by attempting to create a powerful, successful programming language (see also C, Javascript...). 🤣
Daniel Terhorst-North
NK30 :arch: :verified_root:
Benjamin Geer
@exchgr @bilal Alexander Stepanov wasn’t far off with “money oriented programming” http://www.stlport.org/resources/StepanovUSA.html
Lyner
@exchgr also, https://eev.ee/blog/2013/03/03/the-controller-pattern-is-awful-and-other-oo-heresy/ (not my blog, but a good read)
Lizzy Fleckenstein
@exchgr meanwhile functional programming being classless, stateless and moneyless (moneyless because there are no Haskell jobs ;-;)
Tor Iver Wilhelmsen
@exchgr because the struggle came later when someone started implementing multiple inheritance of implementation.
Iron Archer
@exchgr
Medium Endian
I'm absolutely sending this to the supervisor that wrote a python app using multiple inheritance with cyclical references. That was a very educational puzzle for our intern to sort out...
elle mundy
if you’re thinking of explaining to me why my joke is wrong, here’s a little pro tip for you: don’t
Partially Stochastic
@exchgr I prefer declarative programming, where I just declare that my software is working, and leave it at that
Paolo Redaelli
@exchgr |
@exchgr @rmondello bänger tweet