<audy>
pikajude: probably too close to the metal for the clock to time it
<pikajude>
hey ljharb, do you know if it's possible to turn profiling on and off during the run of a node.js program
<ljharb>
i don't think so
<ljharb>
not sure tho
<pikajude>
cool
<pikajude>
i guess that's true for most other languages
<pikajude>
so node.js is saved a steaming hatefuck today
<cloudhead>
:o
<pikajude>
ahahaha
<pikajude>
every guide on the internet tells you to run node --prof
<pikajude>
because apparently every nontrivial node program is just a tiny one-off shell script
<pikajude>
and then load the resulting log file into chrome
<pikajude>
if chrome crashes while trying to load your log file, fuck off
<cloudhead>
I don't think node was ever meant for serious business
<cloudhead>
I don't know why people still try
<pikajude>
oh right, also
<pikajude>
if chrome does load your log file, and 76% of the runtime is in a 5000-node-deep tree whose leaves are all labeled "Unknown", then you can ESPECIALLY go fuck yourself
devyn has quit [Read error: Connection reset by peer]
<alva>
i hate that y'all have to deal with node badness and it also makes me feel less crazy for not having good experiences with it
<alva>
...while seemingly everyone was showering it in praise
<ljharb>
node's great but nobody's saying there's no bad part
<ljharb>
s
<pikajude>
no i agree
<pikajude>
i'm just the guy saying there's no good part
<pikajude>
but keep in mind that's because i'm using 0.10
<pikajude>
before they invented node that isn't shit