<div>
Further to Andy's comment, we also need to remember that many Rails apps start off as prototypes. The prototypes that work quite often make it to a version release, which doesn't always allow for much refactoring. Stuff has to get done quickly and this is what makes Andy's "instant access" valuable. It can also be quite cumbersome to have too many strict rules (and even tests!) when the requirements are in a constant state of flux, which is common in early development stages.
</div>
<div><div><br></div><div>-- </div><div>Ed James</div><div>Sent with <a href="http://www.sparrowmailapp.com/?sig">Sparrow</a></div><div><br></div></div>
<p style="color: #A0A0A8;">On Monday, 2 April 2012 at 11:42, Andrew Stewart wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div><br></div><div>On 2 Apr 2012, at 12:20, Viktor Tron wrote:</div><blockquote type="cite"><div>I don't know who came up with this pattern in rails in the first place, it violates everything you ever wanted objects and instance variables to mean.</div></blockquote><div><br></div><div>True, but you have to admit it's tremendously convenient ;)</div><div><br></div><div>I know it's heretical to say so but I like being able to access instance variables as if by magic in my views. I came to Rails from J2EE / JSP / servlets where accessing controller data in views was outstandingly tedious. I know Rails' approach violates encapsulation and so on...but I like it.</div><div><br></div><div>Cheers,</div><div><br></div><div>Andy Stewart</div><div>----</div><div><a href="http://airbladesoftware.com">http://airbladesoftware.com</a></div><div>_______________________________________________</div><div>Chat mailing list</div><div><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a></div><div><a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>