ec changed the topic of #elliottcable to: a π•―π–Šπ–“ 𝖔𝖋 π•―π–Šπ–™π–Šπ–—π–’π–Žπ–“π–Šπ–‰ π•―π–†π–’π–˜π–Šπ–‘π–˜ slash sΝ”ΜžuΝ•Ν™pΝ™Ν“e̜̺rΜΌΜ¦i̼̜oΜ–Μ¬rΜ™Μ™ c̝͉α»₯Μ§Ν˜αΈ·Μ‘Ν™Ε£Ν“Μ€ || #ELLIOTTCABLE is not about ELLIOTTCABLE
Sgeo has quit [Read error: Connection reset by peer]
Sgeo has joined #elliottcable
prophile has quit [Quit: The Game]
_whitelogger has joined #elliottcable
prophile has joined #elliottcable
mylesborins has quit [Quit: farewell for now]
mylesborins has joined #elliottcable
<ec> fuckkkk
<ec> I need to Not Program, tho
<ec> I'm such a fucking addict
<ec> *days* of my life disappear down the gullet of some hungry shell-script that never even sees the light of day
<ec> I'm such a fucking addictive personality; but drugs, alcohol, Millennial GamblingΒΉ, partying, none of those things hit me too hard
<ec> *just* programming and MMos
<jfhbrook> programming's more satisfying when you ship
<jfhbrook> last time I did programming at home I whipped up the thing but crapped out around packaging and tests
<jfhbrook> this is the kinda thing I geek out about
<ec> I'm the opposite
<ec> I *care about* other stuff more, but I tend to *obsessively attack* packaging, management, testing, documentation tasks
<swart> I like getting distracted by random problems that have nothing to do with what I'm trying to test, and wasting hours of my day tracking down what turns out to be something stupid* [* still haven't figured out what this morning's stupid problem is]
<pikajude> something stupid*
<pikajude> (*note: all problems are stupid)
<swart> well only if they're my own fault. which is a lot of them
<pikajude> today i'm working with a class that has 33 nullable arguments in its constructor
<swart> that sounds unpleasant
<pikajude> :^)
<pikajude> oh, sorry, 27 nullable arguments
<pikajude> 6 of them are non-null
<swart> I've just spent 3 hours trying to find out why I can't get the same results to appear on two different machines
<swart> complaining doesn't help
<jfhbrook> ec: it doesn't help that packaging in python is kinda shitty
<jfhbrook> ec: and, like I get caught up in details--I wanna do it right y'know?
<jfhbrook> in other news though, I finished porting a spark job to python today
<jfhbrook> like put it into review and only got minor comments
<swart> well that was interesting. bug was my bug, but it had been there from the beginning and only showed up with test data
<pikajude> :O
<swart> that's what we get for loading array-valued attributes from relational databases and csv files
<pikajude> is this the beginning of a hex
<swart> dunno. it's now after 1:20 on Friday, I missed lunch and I'm exactly where I was at 4:20 last night
<pikajude> 4:20?? nice
<pikajude> i just received the new jeans i bought in the mail
<pikajude> but they're not the right ones, so i'm depressed
<swart> that's brave
<pikajude> being depressed?
<pikajude> oh
<swart> no ordering clothes in the mail
<pikajude> i mean
<swart> return them I guess
<swart> it's easy to do these days
<pikajude> i thought i was buying some that i had gotten from the same place before
<pikajude> but they are different
<pikajude> the only reason i bought them online is because they weren't in store
<swart> time for lunch
<jfhbrook> yo ljharb who the fuck is this james kyle dude
<jfhbrook> and why do yarn people seem to be so bad at dependencies
<pikajude> yo, yo, yo
<jfhbrook> like, lockfiles shouldn't apply for packages but you should have them anyway
<jfhbrook> subpackages*
<pikajude> i never used yarn
<pikajude> i hope it's good
<ljharb> jfhbrook: james was the second core babel dev, and he helped create yarn at fb
<jfhbrook> so babel is fine
<jfhbrook> yarn sounds like a turd though
<ljharb> it's not all bad
<ljharb> james is a delightful human tho
<jfhbrook> I mean
<jfhbrook> if yarn was a sports they'd be like
<jfhbrook> the pats, or worse
<jfhbrook> they'd be the sf giants >:6
<jfhbrook> seriously, fuck the giants
<jfhbrook> anyway, I'll always root for npm in a brawl
<ljharb> fa sho
<jfhbrook> I had a pretty good conversation with wycats though that night we got yelly about subdep lockfiles in #node.js and he noticed
<ljharb> anything come out of it?
<jfhbrook> I mean
<jfhbrook> I didn't convince him of much
<jfhbrook> but it did remind me that he's ultimately just some dude
<jfhbrook> and like the other time I'd talked with him was like 2011 and like
<jfhbrook> we've all done some growing up
<jfhbrook> his wife was annoyed he was yelling on the internet instead of going to bed, I thought that was funny
<jfhbrook> his thoughts on frameworks, ie the value of ember, are interesting and valid, even if I don't particularly like ember itself
<jfhbrook> like ember's fine, it does all the things, it's a viable alternative to react + all its friends
<jfhbrook> just wasn't my fave the time I worked on an ember app, that's all
<jfhbrook> it was GA event tracking, funny enough
<jfhbrook> this is likely going to be the limit of my kinja FE contributions as well
<ljharb> what's kinja?
<jfhbrook> gizmodo's cms
<jfhbrook> but also technically a medium competitor except apparently nick denton is bad at marketing?
<ljharb> ah
<pikajude> oh
<pikajude> no wonder kotaku, jezebel, jalopnik, and lifehacker all basically look exactly the same
<jfhbrook> like I honestly believe somebody fucked up kinja by not making it really really obvious that they're going toe to toe with medium
<jfhbrook> yeah pikajude it's a unified platform, it's actually pretty dope
<jfhbrook> they also have some pretty solid product people there
<jfhbrook> like the product is on point, it's easy to use, flexible in the ways that matter, rigid in the ways that keep it simple and fun to use
<jfhbrook> fully featured comments system, because that's core to the kinja platform
<pikajude> kool
<pikajude> shame about actual kotaku comments
<jfhbrook> I have some decent news ljharb
<jfhbrook> > One key detail about package-lock.json is that it cannot be published
<jfhbrook> so I can use a package-lock.json if I so wish for development without hosing downstream consumers
<pikajude> some downstream consumers are into being hosed though
<jfhbrook> well npm-shrinkwrap continues to work as before, I think
<jfhbrook> in fact I think the format is backwards compatible
<jfhbrook> yeah, in fact it appears that they're literally the same format, and npm-shrinkwrap.json is used for this latter use case
<jfhbrook> of "real lockfiles," I suppose
<jfhbrook> I guess yarn won that debate
<jfhbrook> you ever see Rat Race?
<jfhbrook> 2001 comedy
<jfhbrook> I keep thinking "maybe it's a secret publicity stunt" except "maybe it's an advisory lockfile"
<jfhbrook> http://www.imdb.com/title/tt0250687/?ref_=fn_al_tt_1 if you've never heard of it
<ljharb> jfhbrook: ok that's really nice, that npm will npmignore them no matter what
<ljharb> so at worst case, my optout will be "gitignore + postinstall script to remove it"
<jfhbrook> oh, yeah--the effect is the same but yeah I think it's actually straight ignored on upload
<ljharb> cool
<jfhbrook> yeah, new docs say that shrinkwrap is only if you're installing to deploy, as with a cli tool or maybe an app
<ec> swart!
<ec> been a while
<ec> somebody catch me up on this lockfile jazz
<swart> holaec
<ec> I barely had time to install yarn for the first time before people started yelling that it was terrible and npm appeared to have subsumed the functionality???
<ec> I'm so bad at keeping up with the JS world outside my little project-directory-bubble
<jfhbrook> yeah, that's the short answer
<jfhbrook> yeah don't feel bad about that, yarn was afaict just an annoying diversion
* swart is looking forward to not learning yet another package manager
<ec> well
<ec> what about the other third-party node_modules managers
<jfhbrook> yarn's the only one with serious adoption afaik
<jfhbrook> anyway, npm 5 supposedly solves the same problems yarn did as compared to 4, but better
<ec> pnpm?
<ec> and that other one?
<jfhbrook> see we can't even remember their names
<ec> lmfao
<ec> pnpm has reasonable adoption and is kept up-to-date
<ec> and there's another that is the same status of Meaningfulness but I've personally never used it
<ljharb> yarn is the only npm option that's ever been viable, altho the others tried hard
* ec nods
<pikajude> yarn also makes node more cat-accessible
<joepie91> ec: you're probably thinking of ied?
<ljharb> didn't ied rename, so it wasn't named after a missile?
<pikajude> that's probably a good idea
<jfhbrook> or the thing that blew up my cousin's stryker in iraq
<jfhbrook> (he was fine, like battery acid damage but no condolences necessary)
<jfhbrook> icbm would be a better name honestly
<joepie91> ljharb: I uh, can see why they would
<joepie91> lol
<joepie91> hm, doesn't seem like they actually renamed though
prophile has quit [Quit: The Game]