> Should theta/R have getters is entirely up to your API decisions But it often isn't. The blog post starts out talking about how that field -> getter/setter p

> Should theta/R have getters is entirely up to your API decisions But it often isn't. The blog post starts out talking about how that field -> getter/setter pattern is very widespread, and tools (JavaBeans tools for example), make that pattern unavoidable sometimes. Yes, it should be an API decision, but for a variety of reasons -- tools, patterns, coding standards, cargo cult programming -- it isn't.