Why OO Sucks by Joe Armstrong (2000)

Re:Why OO Sucks by Joe Armstrong (2000) by treis on Sunday April 21, 2019 @09:19PM (#19715667)

>Well, in my experience, in every almost every code-base (either from functional, or imperative programing), we end up with modules, witch are a set of function taking the same type as a parameter. This is very close to binding the functions and the types...

And the world is not so neatly divided between things that just are (data structures) and thing that do things (functions). Take a date for example. The fact that it is a Wednesday is a "just is" sort of thing but is typically implemented as a function.

[ Parent | on HN ]

Re:Why OO Sucks by Joe Armstrong (2000) by ddebernardy on Sunday April 21, 2019 @11:37PM (#19716324)

I'm not sure I'd agree that it being a Wednesday is a "just is" sort of thing. The point in time is a data point (on the time axis, if you will). A function then needs to place it in a calendar.

FWIW I'm struggling to come up with a good example of where the line between data and functions is clearcut, except perhaps when the data describes a function: an SQL string, some code that'll get eval'ed, etc.

[ Parent | on HN ]

Re:Why OO Sucks by Joe Armstrong (2000) by treis on Monday April 22, 2019 @09:22AM (#19718673)

>The point in time is a data point (on the time axis, if you will)

You need some way to place in on that axis, though. Commonly we use Day, Month, and Year to do so. But we could also define a date as the seventh Wednesday in 2019. Or as an integer relative to Jan 1 1970.

[ Parent | on HN ]