Short answer: It depends.<div><br></div><div>Long answer: Some modules provide functionality for one-off tasks (i.e. Login Destination) and other modules are toolkits that don't do anything immediately out-of-the-box but provide a framework for larger goals (i.e. Rules, CCK, Views, etc). Sometimes the former are a better choice because they are simple and lightweight; sometimes the latter are a better choice because they provide much richer functionality that will be used elsewhere. Depending on what sort of site you are building, either could work, you just have to make a decision about the larger architectural goals of the site.</div>
<div><br></div><div>In your example: if you feel like Rules are useful and you'll be using them elsewhere, you might as well use Rules for everything -- that way you know the functionality for things like redirects are all in one place.</div>
<div><br></div><div>Keep in mind: You can always refactor. We make the best decisions we can at the time in anticipation of what's next, but sometimes we have to make changes down the road due to changing requirements or new technology, or we just see a better way to do it for usability's sake. That's OK, and this exploration and refactoring is just part of the job. You'll be a better developer for knowing the advantages and disadvantages of the methods.</div>
<div><br clear="all"><div><br></div><font color="#333333">Carl Wiedemann</font><div><div><font color="#333333">Website design and development consulting</font></div><div><font color="#333333"><a href="mailto:carl.wiedemann@gmail.com" target="_blank">carl.wiedemann@gmail.com</a> | skype: c4rlww</font></div>
</div><br></div>