News for hackers. Stuff that matters.
Re:Table-oriented programming (2002) by notduncansmith on Wednesday June 22, 2016 @11:54PM (#11958748)
What you're used to seeing might be better described as "class-oriented programming", i.e. Java's take on OOP. Once you realize that `this` is just an implicit parameter and objects are just closures (look at Javascript's OOP for a good illustration of this principle), and you start to think about how objects can interact reliably across interfaces/languages/networks/failures, you more-or-less inevitably end up at "message-oriented programming", i.e. Smalltalk's take on OOP, wrapped up in declarative/functional APIs.

Disclaimer: these ideas are all unoriginal and some of them directly borrowed from other commenters in this thread.

Re:Table-oriented programming (2002) by digi_owl on Thursday June 23, 2016 @04:15AM (#11959523)
All this makes unix core tools and shell scripts sound OO.
Re:Table-oriented programming (2002) by gnaritas on Friday June 24, 2016 @01:53PM (#11971931)
Not really, they're more functional, they have textual input and output, and can be chained together, but they don't really trade meaningful messages back and forth. Processes can be thought of as objects, and signals as messages, but the set is not extensible while OO allows the developer to define the messages.