These are two sides of the same coin, and both of them miss the point. You should be dealing with scale, and you should use a language that allows you to concisely describe how to compute large amounts of data easily. The best part is that once you start writing APL, you’ll feel like a wizard.
Right. A closure can be thought of as an object with a single method.
Alternatively, the core of OOP is objects sending messages to other objects. There are a lot of different ways to do that. A micocontroller sending “begin <process>” to another microcontroller over SPI is OOP. At some point, the way C++ does things became the way to do OOP, and that was a narrow minded mistake.
An object is a poor man’s closure.
A closure is a poor man’s object.
These are two sides of the same coin, and both of them miss the point. You should be dealing with scale, and you should use a language that allows you to concisely describe how to compute large amounts of data easily. The best part is that once you start writing APL, you’ll feel like a wizard.
Right. A closure can be thought of as an object with a single method.
Alternatively, the core of OOP is objects sending messages to other objects. There are a lot of different ways to do that. A micocontroller sending “begin <process>” to another microcontroller over SPI is OOP. At some point, the way C++ does things became the way to do OOP, and that was a narrow minded mistake.