I’m not sure what I supposed to be reading here but the title at least rang a bell of recognition for me. Programming to an interface, composition, immutable c

I’m not sure what I supposed to be reading here but the title at least rang a bell of recognition for me. Programming to an interface, composition, immutable classes and objects as fancy closures that can do more than one thing: Drake-yes-please.jpg Inheritance for code sharing: Drake-no-thanks.jpg. One thing I really miss from my Java days, and which I don’t really think has anything to do with OOP, is the concept of package visibility. Private data for the class itself. Protected data for inheritors if you dare have them. Public for anyone using your library. And package level visibility for me and my team to have special privileged access to these things in the same module, but which one outside of it is allowed to touch. It’s a great feature for large groups of programmers.