To answer the question of why we may want to leave it out: - If you are using remote debugging on ios6+ you don't need it - Our log wrapper has been repeatedly less functional than the system implementation (though we do fix these issues as they are found)
But that does not mean I am arguing against leaving it in by default. Idealist me says 3.0.0 should move everything that can be a plugin out to a plugin. Pragmatist me says this is pretty safe/useful in core. +0 vote here either way. Perhaps we could have a set of "default" plugins that are installed, but can be un-installed? This would give us best of both worlds. -Michal On Tue, Jul 2, 2013 at 1:01 PM, Filip Maj <f...@adobe.com> wrote: > 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" <cmarc...@gmail.com> 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 > > > >
