Re:Alan Kay on the Meaning of “Object-Oriented Programming” ...
by hota_mazi on Monday March 18, 2019 @01:40AM
(#19418921)
> and every object can call the pass method of any other object. It's up to each object to decide for itself what it will do with any given message that it receives.
It's a horrible programming model, though. We should be glad this is not how most languages work.
Re:Alan Kay on the Meaning of “Object-Oriented Programming” ...
by dnautics on Monday March 18, 2019 @02:47AM
(#19419123)
>It's a horrible programming model, though.
Have you ever actually programmed in this model? I wrote a correct RAFT library in ~300 lines of code that are extremely legible using this model.
Re:Alan Kay on the Meaning of “Object-Oriented Programming” ...
by scroot on Monday March 18, 2019 @09:16AM
(#19420739)
> It's a horrible programming model, though. We should be glad this is not how most languages work.
This is not only about languages, but also environments. The argument Kay makes is that in order to make very large complex systems that are resilient, you need something like this kind of message passing. And indeed, this is how the Internet works too
Re:Alan Kay on the Meaning of “Object-Oriented Programming” ...
by hota_mazi on Monday March 18, 2019 @02:27PM
(#19423683)
The Internet works in hundreds of different ways, message passing, RPC, REST, store and forward, propagation, etc...
Re:Alan Kay on the Meaning of “Object-Oriented Programming” ...
by scroot on Monday March 18, 2019 @08:41PM
(#19426944)
It's all made possible because of the protocol which is a kind of message passing. If a node somewhere on the Internet doesn't receive a packet for whatever reason, the whole network doesn't come crashing down.
This seems exactly analogous to how a collection of webservers interact. They can only communicate with each other by tossing a chunk of bytes around hoping that the target knows what it's supposed to be doing with those bytes.