3 ms·

Thanks for the explanation. I got caught up on the "message passing" vs "api" part of your original comment and was wondering how you differentiated between the

by dmux 5y ago

Thanks for the explanation. I got caught up on the "message passing" vs "api" part of your original comment and was wondering how you differentiated between the two. >A good Java API wouldn't have many Setters/Getters that do nothing but set/get references to internal objects, but rather ones that parse and make sense of it's internal state. I completely agree. Getter/Setter obsession often leads to breaking the Law of Demeter in most Java code bases I've seen.

AmpsterMan 5y ago
I'm not the original poster so you should wait for their reply, hah! They may have meant something else. This is just a topic I've spent some time thinking on and wanted to share my own $0.02. My go-to language for personal projects/small tools at work is Java. I think if one looks at Java codebases as strict encapsulation at the package level it becomes a lot more bearable.