Another post which reminds everyone what object oriented programming is about. And yes, there's indeed a variety of different tools in there, not all object oriented languages are equivalent.
I don't get why object oriented programming gets so much flack these days... It brings interesting tools and less interesting ones. Just pick and choose wisely like for any other paradigm.
A talk from Casey Muratori who is pushing his ideas on software architecture. This one is very interesting on the long history detour it does. Shows well how we keep rediscovering stuff which sometimes go back to the early times of computer science.
This is a difference which needs to be reminded. Using precise language obviously helps.
A library bringing the mixins concept to C++.
A funny way to illustrate the principles behind the SOLID acronym.
Didn't know this kind of architectural pattern had a name. Interesting. I wouldn't recommend it in any context though, but one more metaphor to reason with.
Interesting look at the history of inheritance in programming languages. There's clearly still room for improvements on this concept.
Nice state of the art view on how dynamic dispatch is implemented in several languages. Does a good way showing the trade-offs involved.
One of the toughest object-oriented programming principles to apply properly in my opinion. At least it looks like we found a better way to teach it now.
Nice overview of the good uses and wrong uses for classes. We're far from the abuses of the early times now.
A bit C++ and game engine focused (to be expected since this is were this kind of techniques originate from), bit very good explanation on how to have packed layouts for your objects and reduce pressure on memory allocation for data intensive tasks.
Interesting approach. I did quite some of that but without really putting it together like this. It's a nice way to explain it.
A good point... everybody should know at this point that delegation should be favor. So why do we keep turning to inheritance even in cases we shouldn't? Convenience and writing less code mainly. Unfortunately that leads to bugs more often than not.
Interesting move. Looks like Java will get value types at last. Coming from C++ this feels long overdue.
Very good reminder that as an industry we're quick to blame external factors for our own failures. Of course we can be given a bad hand, but sometimes we'd have failed with a good hand as well.
Excellent reminder about where the limit is for the compiler to optimize things. Nowadays it's mostly about the memory accesses and then it means that the design matters a lot. Object-oriented designs being far from optimal here. Data-oriented designs fare much better but are definitely less friendly for human brains to reason about them.