Explore >> Select a destination
|
You are here 
|
golangtutorials.blogspot.com | ||
| | | | |
aneesh.mataroa.blog
|
|
| | | | | ||
| | | | |
www.ardanlabs.com
|
|
| | | | | Introduction I see a lot of developers coming to Go from object oriented programing languages such as C# and Java. Because these developers have been trained to use type hierarchies, it makes sense for them to use this same pattern in Go. However, there are aspects of Go that don't allow type hierarchies to provide the same level of functionality they do in other object oriented programming languages. Specifically, the concepts of base types and subtyping don't exist in Go so type reuse requires a differ... | |
| | | | |
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. | |
| | | | |
rachelcarmena.github.io
|
|
| | | Some characteristics of functional programming | ||
