/explore
|
You are here 
|
golangtutorials.blogspot.com | ||
| | | | |
krakendev.io
Subclassing can suck. There are so many ways to get it wrong and it's so easy to fall into anti-patterns when you create such a tight coupling between two classes. Most of the time, the need for subclassing can actuallybe replaced by abstraction through protocol-oriented, value-oriented, and functional programming. In fact, I may even argue that doing it that way can far outweigh the "benefits" of subclassing the majority of the time. |
|
| | | | | ||
| | | | |
usethe.computer
[AI summary] A deep technical exploration of open recursion in object-oriented programming, using C++ and Python closures to demonstrate how late binding enables frameworks. |
|
| | | | | ||
| | | | |
www.minaandrawos.com
Ever considered implementing a class factory in Golang (Go) which is a programming language that is not fully object oriented in nature? |
|
| | | | | ||
| | | | |
www.jeremykun.com
Last time we worked through some basic examples of universal properties, specifically singling out quotients, products, and coproducts. There are many many more universal properties that we will mention as we encounter them, but there is one crucial topic in category theory that we have only hinted at: functoriality. As we've repeatedly stressed, the meat of category theory is in the morphisms. One natural question one might ask is, what notion of morphism is there between categories themselves? |
|
| | | |||
