News for hackers. Stuff that matters.
Re:Class Hierarchies? Don't Do That by porker on Sunday March 30, 2014 @02:16PM (#7497167)
> It turns out that our knowledge of the behaviour of non-trivial domains (like zoology or banking) does not classify into a nice tree, it forms a directed acyclic graph. Or if we are to stay in the metaphor, it’s a thicket.

That completely chimes with my experience. I wondered if I was doing OOP wrong, as any time the size/complexity of a project (or module) gets above a certain level, a Thicket results in my code.

> Classes are the wrong semantic model, and the wisdom of fifty years of experience with them is that there are better ways to compose programs.

Where's your source/links? What? This needs expanding - if there are better ways, outline your evidence and show us where we're going wrong :)

Re:Class Hierarchies? Don't Do That by mamcx on Sunday March 30, 2014 @09:58PM (#7499064)
That was sometime I want to ask too.

Probably is the go OO-model?

Re:Class Hierarchies? Don't Do That by thro2 on Sunday March 30, 2014 @07:16PM (#7498403)
yeah. what's a better semantic model?