Mostly I agree with that statement. If you going to use the attribute, then you need to use it. You have to take a hit at some point.
I rember using a world class ORM tool in jaav that allowed join fetches for first elvel attributes for perfroamnce. While I dont expect that of this api for some time yet, I think the idea behind an object model is for me to make it as seamless as possible. Having to call a get method for an attribute breaks my "perception" of using an object. Makes me do more work, breaks my consistancy of code etrc... But there is a ticket so that good :-)
