does it make that much difference or am i splitting hairs?
Well, in this particular case, you might be splitting hairs a bit, but behind the superficial face of your question lies a much bigger one. That is, should I use a module, or write my own equivalent code? I think the answer to that depends on the situation, but I'd bet more often or not the module is the way to go.
There are many reasons, and this has been discussed at great length in the past, but for me the biggest reason is bugginess. Code has bugs; this is a fact. Using a module often helps mitigate the effect of this problem. Perhaps you could argue that the extra complexity of a module adds the chance for even more bugs, but I would counter that the most egregious bugs are of the semantic variety. These are the kind that modules are great for. Once discovered, fixing the module fixes the bug everywhere. It's an instant win, and a compelling reason to stick with the module over the (possibly simpler) hard-coded solution.
As a final note, I should mention that arguing against modules, per se, in terms of efficiency is almost always a losing proposition. In this case, I would bet dollars to cents that the time it takes to send the cookie over the network is an order of magnitude higher than the time it takes to generate the cookie, module or not.
In reply to Re: When to use modules?
by revdiablo
in thread When to use modules?
by wolfi
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |