Effective Java states “you should make each class or member as
inaccessible as possible”. I don't want to create open-ended code, as
that basically means we are going to break people without knowing it.

The general idea is to make sure we know if someone needs to subclass
things. Marking it final forces someone to contact us, then we can
document the extension vs leaving it open ended. In the mean time,
yeah composition will work in many cases.

Make sense?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/70#issuecomment-61279405

Reply via email to