> 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.
