News for hackers. Stuff that matters.
Re:OOP Is Dead, Long Live OOP by zdmc on Thursday October 18, 2018 @05:05PM (#18252107)
A good heuristic: if you’re not dealing with “state” (i.e., Games, DB ORM, Reinforcement Learning), then don’t use OOP
Re:OOP Is Dead, Long Live OOP by bribri on Thursday October 18, 2018 @10:57PM (#18253957)
I completely agree. Use it carefully if you need it but it shouldn't be the default.
Re:OOP Is Dead, Long Live OOP by lerno on Thursday October 18, 2018 @05:10PM (#18252159)
Really? I’d say the accidental distribution of state across objects due to cross cutting concerns is exactly where OO breaks down for me.
Re:OOP Is Dead, Long Live OOP by Hodgman on Thursday October 18, 2018 @07:12PM (#18253139)
If cross-cutting concerns are making your architecture unwieldy, you likely haven't used composition enough / are doing OOP the bad way (tm).
Re:OOP Is Dead, Long Live OOP by lerno on Thursday October 18, 2018 @07:49PM (#18253317)
No, some logic simply isn’t cleanly decomposable, plus the main problem here is that objects lets you get away with implicit state (e.g. if (this.x == 0) doA() else doB(); ) for long enough that when you start realizing you need explicit state, it’s usually distributed quite a bit.