The only one I can think of is a production environment to try to save on a few kb of footprint and a few initialization cycles. I don't think it's worth removing entirely from core, though. Instead, try to make the built-in Logger plugin as easily removable as possible.
On 7/2/13 9:57 AM, "Marcel Kinard" <[email protected]> wrote: >Are there a scenarios where it would be good to not have Logger in an >app, such as permissions, footprint, or just not needing any logging >functionality? I'm having a tough time thinking of any, so I'd also say: >+1 leaving Logger in core >
