> > > What happens when you want to use a module that *doesn't* speak that > lingo? >
Ideally, you would submit a pull request. :) In practice, I will also provide adapters so that you can pass a configured emitter for my logger to the library's log callback. This won't give you source filenames for each message (I don't want to examine the call stack, as I assume that's slow), but it will work with the rest of the featureset (including, especially, log context). If the library doesn't do any logging at all, that obviously won't help; you'll have no options other than a pull request. Using Bunyan everywhere, and configuring filters when viewing the logs rather than in the program, would work; but as you mentioned, that wouldn't be a good idea for standalone libraries anyway. It would also end up consuming lots of disk space for library trace that I know I'll never need. (this would be especially problematic for trace coming from a mobile browser) As for DTrace, I want Windows support. I also want something which can be configured more simply for people just getting started; I want to minimize the learning curve at each end. (I have nice ideas for a middleware-style config system which can be both simple and complicated at the same time) On Friday, April 19, 2013 12:58:44 PM UTC-4, Isaac Schlueter wrote: > > > But basically, my whole goal here is to provide a framework that is > meant > > to be used by libraries as well. > > Do you think that fits in with the Node philosophy? > > Well... It sounds quite a bit less simple than is strictly necessary. > > > Are there any problems with this approach that I'm not seeing? > > It's a little bit ocean-boiling. You have to get all these different > utils to all speak the same language, and effectively craft your own > island of compatibility. What happens when you want to use a module > that *doesn't* speak that lingo? > > If you use Bunyan in your components, you can direct them all to the > same log file, and then "turn on" or "turn off" is just a matter of > configuring whatever viewer to show you what you want. > > If you want dynamic tracing at run-time that can be zero-overhead when > not enabled, then perhaps what you're really looking for is DTrace? > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
