<ec>
no, *school* is easy. My own complete lack of self-motivation when it comes to anything whatsoever except programming, is kicking my ass.
<ec>
I yak-shaved myself into missing a midnight deadline on an assignment last night 'cuz LaTeX.
<ec>
pretty pissed at myself about that.
<ec>
otoh, if u all wna see what my days look like right now, http://ell.io/i1kiKC
<ec>
wtf y
<pikajude>
noice
<pikajude>
right now i'm working on figuring out why the return value of ip.address() in node.js is changing based on what dependencies I have installed
<gq>
i was thinking latex like fetish gear
<gq>
and was like damn son what are you majoring in
<pikajude>
but to be fair
<pikajude>
on this network, there's no guarantee that one's IP won't change every 3 seconds or so
<krainboltgreene>
ec: 20% of their nodes went down.
<pikajude>
-what
<purr>
<prophile> people find human cloning repulsive, why not identical twins
eligrey has joined #elliottcable
<pikajude>
ok so I THINK the error is happening because if you link in a dependency instead of installing it, require ends up using the wrong cache
<pikajude>
or something
<pikajude>
idk
<pikajude>
the fact that this is an error that can happen baffles me
<pikajude>
who thought of this shit
eligrey_ has joined #elliottcable
eligrey has quit [Ping timeout: 245 seconds]
<purr>
<devyn> guise, I'm too high for this shit
<pikajude>
I would rather use php than node
<Hrorek>
pikajude, really?
<pikajude>
I'd rather use brainfuck than node
<pikajude>
because brainfuck doesn't require npm
<gkatsev>
lol
<purr>
lols
<gkatsev>
from all the package managers i've used, npm is by far the best
<gkatsev>
package management is hard
<purr>
<ec> gleaming fucking love sword.
<pikajude>
yeah
<pikajude>
i've used package managers other than npm, so i can definitely say npm isn't the best
<pikajude>
actually, that's not fair. i'm not sure who to blame here
eligrey_ is now known as eligrey
<pikajude>
doh. in the end, it was incredibly simple
<pikajude>
it was npm after all
<pikajude>
the parent package and the child package depend on two versions of the ip library
<pikajude>
the child package defines a test helper that stubs out ip.address()
<pikajude>
but once there are two versions of the ip library present, only one of them gets updated in the require cache
<pikajude>
i knew it would be something like that
<pikajude>
say what you like about npm
<pikajude>
but the way it silently causes behavior changes when something you depend on updates its dependencies
<pikajude>
now that is insidious
<pikajude>
that's some esoteric language shit
<pikajude>
inb4 "well that's how npm works, you should have prepared for it"
<pikajude>
hey maybe if there was literally any way to make any kind of assumptions about the performance or behavior of a javascript program before runtime it wouldn't be such a pain