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
_whitelogger has joined #elliottcable
_whitelogger has joined #elliottcable
gkatsev has quit [Remote host closed the connection]
IRCFrEAK has joined #elliottcable
IRCFrEAK has left #elliottcable [#elliottcable]
gkatsev has joined #elliottcable
<elfboy> ICE CREAM
<jfhbrook> noted.
<pikajude> we all scream
prophile has quit [Quit: The Game]
mylesborins has quit [Quit: farewell for now]
mylesborins has joined #elliottcable
mylesborins has quit [Quit: farewell for now]
mylesborins has joined #elliottcable
Gavriel has joined #elliottcable
Gavriel is now known as gqbrielle
prophile has joined #elliottcable
<ec> hello
<ec> it is a bad weekend
<pikajude> yea
<pikajude> it's shit
<jfhbrook> I just like ultra coincidentally looked up that song the other day
<ec> what song
<jfhbrook> bad weekend
<jfhbrook> it's the only art brut song I really know all that well
<jfhbrook> because I got it off a buddy's external in college
<jfhbrook> but yeah
<jfhbrook> warning, the singer is kinda sorta bad
<ec> wtf
<jfhbrook> ahaha
gqbrielle has quit [Read error: Connection reset by peer]
<prophile> dongs
<jfhbrook> I'm currently trying to build node 0.6 because I swear to god you used to be able to have a variable called 'class' in node
<jfhbrook> but as far back as 0.10 that was not the case
<pikajude> just call it klass
<jfhbrook> ugh but klass is dumb
<jfhbrook> I like class_
<pikajude> call it classs
<jfhbrook> I see cls in python a lot but -_-;
<ja> in C# you can call it β€œ@class” :B
<ec> prophile
<jfhbrook> that sounds like a good online handle
<jfhbrook> @prophile
<prophile> thanks I think
<ec> jfhbrook: ... he's in this room ...
<jfhbrook> oh
<jfhbrook> hi
<ec> ...
<prophile> hello
<ec> .... ... . .. .. .
<ec> twitter.com/prophile
<ec> lol
<jfhbrook> I don't have a names list on the sidebar or anything
<ec> actually he might still be arplyn
<prophile> he is
<jfhbrook> honestly thought it was a play on words
<ec> arplynn*
<prophile> twitter.com/arplynn
<prophile> <shameless self-promotion>
<ec> and jfhbrook, `class` has been reserved since fucking ES1.0
<jfhbrook> dang
<ec> if it ever worked as a bareword identifier in your code, then it's an engine-oddity
<jfhbrook> I wonder what I was thinking of
<jfhbrook> maybe it really was Class
<prophile> we need languages with proper unicode support
<jfhbrook> agree
<prophile> you could call it class but substitute one of the characters for a suspiciously similar looking russian or greek character
<ec> well, there's property names β€” many of those things, again engine-dependent, may be used as *property names*, when the code is not in strict-mode
<ec> iirc
<jfhbrook> ahhh
<ec> and even then you can still use strings, so
<ec> foo['class'] is always valid, though not necessarily kosher or a good idea :P
<ec> foo.class works most places β€” iirc there's something about strict mode? I bet ljharb can answer that
<ec> class.whatever or class() though should absolutely never work
<jfhbrook> lol it works in 0.6 but not in 6
<ec> it seriously works in node 0.6
<ec> O_O!af
<jfhbrook> nono
<jfhbrook> { class: 'foo' }.class
<jfhbrook> that works in 0.6
<jfhbrook> but not in 6
<ec> ahhhh
<ec> hm, so which part: the literal's key-name, or the property-access?
<jfhbrook> the property access
<jfhbrook> the key name appears to work in both
<ec> okay, this contradicts that: http://stackoverflow.com/a/17911822/31897
<ec> if anything, the *opposite* should be true β€” 0.6 wasn't yet full ES5 support, was it?
<ec> wtf
<jfhbrook> weird
<jfhbrook> it works in the repl on 0.6 but not in node -pe
<ec> ahhah.
<jfhbrook> for 0.6 only
<ec> ({ class: 'foo' }).class
<jfhbrook> ooh
<jfhbrook> yeah, parens
* ec laughs
<jfhbrook> so weird
<ec> repl was *weird* early on
<jfhbrook> with parens it works in lts
<ec> holy shit
<ec> an absolutely *marathon* debugging session (spread over several weeks basically) later,
<ec> I discover that `return result is not false` DOES NOT COMPILE INTO WHAT I THOUGHT IT WOULD
<ec> fucking coffeescript
<ec> who where when *ever* would have found `result === !false` useful.
<jfhbrook> olololo
<jfhbrook> what did you think it was?
<ec> result != false
<ec> result !==* false
<ec> WE AT THE HOTEL, MOTEL, COFFEESCRIPT INN
<ec> well that's five more passing tests πŸ™„
<jfhbrook> oh man that's evil
<ec> RIGHT!?
<ec> fuck, I cannot *wait* to rewrite this entire thing in bare ES5.
<ec> well, in the IE6-shimmable parts of ES5.
<ec> I *still* love the way CoffeeScript looks
<ec> it yields such beautiful, beautiful fucking code ;_;
<ec> so readable so clear ... when it works *at all*
<ec> coffeescript is in the correct *direction*, I'm so very sure of it.
<pikajude> by yields
<pikajude> do you mean the pre generation phase
<ec> yeah the design results in beautiful code
<pikajude> ok
<pikajude> so not the generated code
<ec> oh god no
<ec> but transpilers are doomed for that so Β―\_(ツ)_/Β―
<pikajude> hey, what do you all think is the best way to get services set up for a development environment
<pikajude> like
<pikajude> postgres
<ec> deffo something something containers something.
<pikajude> should i just have postgres running on my computer and use that
<pikajude> yes
<pikajude> that's what i thought ec
<ec> ew nah not in 2017
<pikajude> but i'm not sure what the best way to do it is
<ec> okay so there's three ways as I see it:
<ec> most straightforward but least flexible and powerful is just install docker and docker-machine locally;
<ec> slightly more awesome is to use vagrant to maintain a CoreOS docker-host in a VM (VirtualBox or, if you've already paid for it, VMware),
<ec> and awesomest is to have a docker-host in the house running CoreOS on the metal :P
cloudhead has joined #elliottcable
<ec> cloudhead!
<pikajude> ok but
<pikajude> when i'm running my executable locally
<pikajude> how do i connect it with the postgres that's running somewhere else
<ec> 90% of containerization is networking knowledge I guess
<cloudhead> ec: :D
<pikajude> but if i have to manually configure the network when setting up the docker image
<ec> basically, each docker container describes some services that it exposes, and the internal ports that it exposes them on;
<pikajude> how is that any better than running postgres locally and just connecting to that
<ec> then when you *launch* the container from a host, you describe what local ports on the host you want it opened up to
<pikajude> yeah i know
<ec> usually, nothing is opened up to the network at large β€” all connectivity is over a tunnel
<pikajude> i could set up a docker image that imports my seed SQL file and runs postgres
<pikajude> but
<ec> so from your perspective, Postgres will just be running on `localhost:26811` or something
<pikajude> then i gotta configure my program to connect to that
<pikajude> there's still a manual step
<ec> ahhah so that's touching on a big complicated ops problem, just in the small: discovery.