[deleted]
The Big OOPs: Anatomy of a Thirty-Five Year Mistake
31–40 of 193 posts
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#32And on the other end of the spectrum, you have the proponents of Domain-driven design (DDD)[0], where they use an ML descended language such as F# and the aim is to make invalid states unrepresentable by the program [1] [0] https://fsharpforfunandprofit.com/ddd/ [1] Make invalid states unrepresentable: https://geeklaunch.io/blog/make-invalid-states-unrepresentab...
There is a good book on DDD in F#, Domain Modelling Made Functional
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#33Entertaining. The presenter obviously doesn't like the class hierarchy to correspond to the domain model. He seems to think that this was an essential feature of OOP, supported by some quotations by Smalltalk exponents. But not even the Smalltalk world could agree on what OOP actually is (just compare the statements by Kay with the actual architecture of Smalltalk-76ff) and as quickly as Smalltalk lost its significan…
Did you actually watch it? He talks A LOT more about Simula and C++ than Smalltalk. He goes back to the original sources: Kristen Nygaard and Bjarne Stroustrup. Seems odd to focus on Smalltalk when that’s not what the talk was about.
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#34And on the other end of the spectrum, you have the proponents of Domain-driven design (DDD)[0], where they use an ML descended language such as F# and the aim is to make invalid states unrepresentable by the program [1] [0] https://fsharpforfunandprofit.com/ddd/ [1] Make invalid states unrepresentable: https://geeklaunch.io/blog/make-invalid-states-unrepresentab...
There is a good book on DDD in F#, Domain Modelling Made Functional
Yes! I just got a copy of this a couple of days ago. Ive been on a DDD + FP kick recently and it’s leading to some really satisfying solutions.
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#35Earlier quoted context omitted.
He literally gives extensive primary source citations to show that the originators of OOP presented this class-domain correspondence as the correct way to think about and do OOP. Bjarne Stroustrup is not just some random guy.
Is it fair to blame all of OOP for C++?
Maybe not fair, but it’s pretty normal for people to assess paradigms based on their most popular implementations.
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#36Earlier quoted context omitted.
No help. It's video speed. I can read at several thousand words a minute. So I need the whole transcript in one shot. Then I can read it in 10 or 15 minutes or so, and decide if it's worth watching a 2 hour plus video. The answer is almost always "no".
A few lines of Javascript in the console can copy that to the clipboard for you. Maybe someone's packaged that up already. (It's on my todo list to look around...)
Control Panel for YouTube [1] has an option to add a new "Download" item to the menu in the video Transcript box (which I've just noticed is currently broken, as YouTube must have changed the implementation again recently)
Here's a fixed version [2] - run this when the transcript is open and loaded.
[1] https://soitis.dev/control-panel-for-youtube
[2] https://gist.github.com/insin/cb938324866c511066bcabe230b6a6...
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#37Earlier quoted context omitted.
He literally gives extensive primary source citations to show that the originators of OOP presented this class-domain correspondence as the correct way to think about and do OOP. Bjarne Stroustrup is not just some random guy.
Is it fair to blame all of OOP for C++?
yes, because java and c# (and others, python to a certain extent) basically copied it. even ruby, which at its core is about "message passing" sure does a hell of a lot to hide that and make it feel c++ ish. i would bet at least 25% of ruby practitioners arent aware that message passing is happening.
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#38Can someone point to a real life example or tutorial/guide of the ECS architecture he proposes?
I'd like to learn more about how to implement this.
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#39Can someone point to a real life example or tutorial/guide of the ECS architecture he proposes? I'd like to learn more about how to implement this.
Re: The Big OOPs: Anatomy of a Thirty-Five Year Mistake
#40Earlier quoted context omitted.
Is it fair to blame all of OOP for C++?
yes, because java and c# (and others, python to a certain extent) basically copied it. even ruby, which at its core is about "message passing" sure does a hell of a lot to hide that and make it feel c++ ish. i would bet at least 25% of ruby practitioners arent aware that message passing is happening.
[deleted]