The faster you unlearn OOP, the better for you and your software

Post by gerbilly » Sun, Nov 25, 2018, 2:02 PM UTC

crazygringo wrote: post #28

A lot of these initial points I don't think are relevant -- you can model your data in objects, data structures are complex because business needs are complex, data models wind up having implicit graph dependencies as well... BUT, "cross-cutting concerns" is where I think the main valid argument is. In my experience, OOP is just way too restrictive of a model, by forcing you to shoehorn data and code into an object h…

Post by donatj » Sun, Nov 25, 2018, 2:09 PM UTC

ced wrote: post #40

I've never liked classical OOP much, but multiple dispatch is a lovely paradigm. One doesn't define _classes_ per se, but rather just plain old boring structs. struct Player xp::Int end struct Monster hp::Int end function hit(p::Player, m::Monster) p.xp += 10 m.hp -= 20 end The nicest thing is how one one doesn't need inheritance to "add a method" to an object. One just defines my_function(s::String) to be whatever,…

Post by vnorilo » Sun, Nov 25, 2018, 2:11 PM UTC

Post by mabbo » Sun, Nov 25, 2018, 2:14 PM UTC

Post by jcelerier » Sun, Nov 25, 2018, 2:17 PM UTC

ced wrote: post #40

I've never liked classical OOP much, but multiple dispatch is a lovely paradigm. One doesn't define _classes_ per se, but rather just plain old boring structs. struct Player xp::Int end struct Monster hp::Int end function hit(p::Player, m::Monster) p.xp += 10 m.hp -= 20 end The nicest thing is how one one doesn't need inheritance to "add a method" to an object. One just defines my_function(s::String) to be whatever,…