Email or username:

Password:

Forgot your password?
elle mundy

who called it object oriented programming and not class struggle

63 comments
ティージェーグレェ

@exchgr hilarious.

Alan Kay gave it the term.

"I made up the term object-oriented, and I can tell you I did not have C++ in mind."

Though, as far as I've observed Alan Kay is pretty aware of his privilege. I don't know if he's classist? ;)

He is opinionated: youtu.be/Lb-cKVxmVGk

I *think* he referred to it as "Object Oriented" because he was inspired by Sketchpad:

youtu.be/495nCzxM9PI

So, the way Sketchpad rendered objects are manipulated and there is inheritance to "child" objects when a "master" object (as in "master drawing" and Alan May describes how they are now called "classes" because of Simula) is modified for example.

(Dr. Ivan Sutherland [the creator of Sketchpad] was Alan Kay's doctoral advisor and one of the tasks Alan Kay had to do as a grad student was port Sketchpad to different hardware than what it was originally written to use)

@exchgr hilarious.

Alan Kay gave it the term.

"I made up the term object-oriented, and I can tell you I did not have C++ in mind."

Though, as far as I've observed Alan Kay is pretty aware of his privilege. I don't know if he's classist? ;)

He is opinionated: youtu.be/Lb-cKVxmVGk

I *think* he referred to it as "Object Oriented" because he was inspired by Sketchpad:

elle mundy

@teajaygrey he also regretted naming it that, wishing he’d focused more on the point, which was the messaging between objects

ティージェーグレェ

@exchgr sure, but looking at Sketchpad and knowing Alan Kay's relationship to it, perhaps we can at least understand his rationale at the time?

IMHO, many in the field never understood object-oriented paradigms well at all. I only postulate that perhaps if they were more familiar with its backstory they might have a better comprehension of its etymology if nothing else.

There are similar paradigms, from other fields, e.g. recursion in mathematics and Linguistics (which sure, exists in programming too, but how many people talk about "recursive oriented programming"?)

@exchgr sure, but looking at Sketchpad and knowing Alan Kay's relationship to it, perhaps we can at least understand his rationale at the time?

IMHO, many in the field never understood object-oriented paradigms well at all. I only postulate that perhaps if they were more familiar with its backstory they might have a better comprehension of its etymology if nothing else.

Ó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).

ティージェーグレェ

@MyLittleMetroid The back story behind SmallTalk is fascinating too. I'm not at a laptop to dig it up presently, but it was done almost as a dare.

My crude summary: SmallTalk was created essentially to prove a point that a powerful program could be implemented in approximately a page of code.

Albeit, it grew from that original proof of concept.

If you ever have an opportunity to visit DynamicLand in Oakland, it embodies a similar ethos. No surprise, Alan Kay was one of the individuals behind that research project.

They have a section where the operating code is all printed out on a board and the core kernel again: is basically just a page of code.

Albeit, the underlying complexity (implemented atop Lua, which is atop a bunch of other stuff) is obfuscated in that presentation, but: it's a welcome obfuscation. It allows the users to keep things simple and powerful and intuitive and elegant. It's a fascinating brainstorming work shop. Essentially making prototyping powerfully interactive systems as superficially simplistic as child's play in a preschool.

After visiting it, from my vantage at least: it became painfully clear both how far ahead visionaries such as Alan Kay and his collaborators are, and how far behind almost everything else in the field remains.

@exchgr

@MyLittleMetroid The back story behind SmallTalk is fascinating too. I'm not at a laptop to dig it up presently, but it was done almost as a dare.

My crude summary: SmallTalk was created essentially to prove a point that a powerful program could be implemented in approximately a page of code.

Albeit, it grew from that original proof of concept.

Ó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...). 🤣

Michael / Chgowiz 🎲🎲

@exchgr Hm. I feel like your suggested label is polymorphic in nature...

Abhijit

@exchgr who are you.. so wise in the ways of science?

arclight

@exchgr We were warned about inheritance, especially multiple inheritance...

Daniel Terhorst-North

@arclight @exchgr “It’s called inheritance because your grandchildren will still be clearing up the mess you made with it.”

Andrew Feeney

@dcoderlt @exchgr If it was working I wouldn’t be here trying to fix it now would I?

NK30 :arch: :verified_root:

@dcoderlt @exchgr Because the working class usually is the majority of the population, which doesn't really fit a class with only a single instance?

Michał Górny

@exchgr, they actually meant to say "oops" but had an off-by-one error.

mllaneza

@exchgr
That'd fit better with what I produce.

Benjamin Geer

@exchgr @bilal Alexander Stepanov wasn’t far off with “money oriented programming” stlport.org/resources/Stepanov

ngmi

@exchgr
When I do it it's called disoriented programming
@person72443

Lyner

@exchgr because not everyone uses Java or C++

sz_duras

@exchgr in class struggle classes inherit through language, ideology and machines…

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.

Tarcio

@exchgr FactoryFactoryFactorySingletonManager

Iron Archer

@exchgr
same fool who called it stress free packaging instead of instant blood pressure raising packaging

Medium Endian

@exchgr

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

Andrej

@exchgr Who called it "functional programming" and not "Smash the state"?

Ptx

@mastodon.world man i just don't know who to follow in here.

Marc

@exchgr because object oriented programming is about sending a message ;)

Demian

@exchgr some classes are deliberately overloaded

Resuna

@exchgr ObPedant: not all OO languages have classes

bignose

Choose your side: private, protected, or public

@exchgr

👻 Feufochmar
@exchgr there exists class-less object-oriented programming.
Niels Abildgaard

@exchgr Nothing to lose but our type system

natriumchloride

@exchgr its abbreviation is 'oop' though so there's that at least xd

Paolo Redaelli

@exchgr
Because OOP was never centered on classes but on messaging between objects. Classes is a typing taxonomy

Ian

@exchgr not sure but my code is often dysfunctional

D.C.U.K.

@exchgr I guess the prototype was really based, or something.

Go Up