@dan_jenkins @davidmarkclem I need to find a way to avoid paying a perf penalty for that :/
-
-
Replying to @matteocollina
@matteocollina@davidmarkclem ok :) its the only thing stopping me from easily moving projects to use pino I think :)1 reply 0 retweets 0 likes -
Replying to @dan_jenkins
@dan_jenkins@matteocollina maybe it should be a separate module1 reply 0 retweets 0 likes -
Replying to @davidmarkclem
@davidmarkclem@matteocollina it'd be a bit of a pain but an understandable one to keep pino small and faster1 reply 0 retweets 0 likes -
Replying to @dan_jenkins
@dan_jenkins I will need to use new Function(), do I have a go@davidmarkclem?1 reply 0 retweets 0 likes -
Replying to @matteocollina
@matteocollina@dan_jenkins ahhhh is there no other way, also thoughts on sep mod? Let's get a proper talk2 replies 0 retweets 0 likes -
Replying to @davidmarkclem
@davidmarkclem@dan_jenkins I think I have a way keeping the same structure and without using new Function. I’ll give a try tomorrow1 reply 0 retweets 0 likes -
Replying to @matteocollina
@matteocollina just became aware of Pino; Bole perf was a bit of a thorn in my side. Thanks for making this! :D@davidmarkclem@dan_jenkins1 reply 2 retweets 2 likes -
Replying to @yoshuawuyts
@yoshuawuyts Pino is a month old :D Done as a side effect of sticking ne and@davidmarkclem together for a week and a half. cc@dan_jenkins2 replies 0 retweets 2 likes -
Replying to @matteocollina
@matteocollina haha, that's pretty great! Just tested it on a lil bench project and it's fast heypic.twitter.com/AY4KQTxXp9
1 reply 0 retweets 0 likes
@matteocollina first test was bole, second was pino. I'll see if I can update garnish to parse pino output too - https://github.com/mattdesl/garnish …
-
-
Replying to @yoshuawuyts
@yoshuawuyts with the slowtime option you will get the same output of bunyan. But it’ll be 20% slower, seehttps://github.com/mcollina/pino/pull/5 …0 replies 0 retweets 2 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.