ec changed the topic of #elliottcable to: a π―ππ ππ π―πππππππππ π―ππππππ slash sΝΜuΝΝpΝΝeΜΜΊrΜΌΜ¦iΜΌΜoΜΜ¬rΜΜ cΜΝα»₯Μ§ΝαΈ·Μ‘ΝΕ£ΝΜ || #ELLIOTTCABLE is not about ELLIOTTCABLE
prophile has quit [Quit: The Game]
cloudhead has joined #elliottcable
_whitelogger has joined #elliottcable
cloudhead has quit [Ping timeout: 240 seconds]
fujisan has joined #elliottcable
cloudhead has joined #elliottcable
mylesborins has quit [Quit: farewell for now]
mylesborins has joined #elliottcable
prophile has joined #elliottcable
kier has quit [Quit: No Ping reply in 180 seconds.]
kier has joined #elliottcable
cloudhead has quit [Ping timeout: 260 seconds]
<ja>
hey, i'm active
<pikajude>
ja, you are
<ja>
hi pikajude!
<pikajude>
that's what they all say
<ja>
:<
<ja>
let's talk about Paws then
prophile has quit [Quit: The Game]
<ja>
damn it, The Game
<jfhbrook>
ljharb: anyone PR ayo support to nvm yet? asking here cause I don't wanna cause a kerfluffle
<ljharb>
but basically, i <3 all the people doing ayo, and i <3 what they want to do, but i think a fork is a really dumb way to go about trying to do it - and my suspicion is that most of their complaints will be largely resolved in the coming weeks (but we'll see)
<ljharb>
and then from a more objective viewpoint, ayo is nowhere near ready to be supported or used by anyone
<jfhbrook>
yeah I feel you
<ljharb>
see the list of 5 criteria i posted in that issue
<ljharb>
(which objectively applied to io.js when i added support)
<ljharb>
there were clear technical reasons to use `iojs` over `node`; it's not a very strong argument to use ayo until there's clear technical reasons to do so
<ljharb>
the way i built iojs makes it relatively trivial to add support for ayo, ofc
* ja
had not heard of ayo
<ja>
did they just fork node for fun?
<ljharb>
no
<ljharb>
they forked node for very valid and important inclusivity and community management reasons
<ja>
their readme is pretty sparse
<ja>
oh
<ljharb>
buttttt a fork is a really weird approach to fixing those problems, and they did it within a week of the drama happening
<ljharb>
we'll see tho
<jfhbrook>
ayo is strictly a political statement at this point, at least barring a bunch of ctc people jumping ship
<jfhbrook>
it *could* be a real thing
<jfhbrook>
but it's not *yet*, and most people are in a wait-and-see holding pattern
<ljharb>
right
<jfhbrook>
imo the only reason iojs succeeded was because they were able to make most of the people involved, ie the ctc's predecessors, move to the new project immediately
<ljharb>
i don't even think it's that
<ljharb>
it's because nothing had happened in node for years
<ljharb>
and it was plainly obvious that joyent via tj controlled node and was forcing it to stagnate
<ljharb>
iow there was years of good faith effort to fix the project before they bailed
<ljharb>
(public, loud, good faith effort)
<ljharb>
here there was tons of effort for awhile, but none after the explosion surfaced to a large group of people
<ljharb>
anyways i don't want to like, tone police them, or anything
<ljharb>
they're in the right and their haters are POSsesses
<ljharb>
but i still don't agree with the approach Β―\_(γ)_/Β―
<jfhbrook>
I think a lot of people have been trying to fix the rod situation for a long time but behind the scenes
<jfhbrook>
think years
<jfhbrook>
and no I don't think you're tone policing or being a shitlord, you just want to feel like people have tried to fix this properly, in good faith
<jfhbrook>
and I agree that this hasn't been exhausted, yet
<jfhbrook>
but the stuff with the inclusivity wg was years ago
<ljharb>
a year, yeah
<ljharb>
but these issues weren't really raised publicly then, it seems
<jfhbrook>
no, they weren't
<jfhbrook>
it sounds like they really did try to exhaust their options in a private setting
cloudhead has joined #elliottcable
fujisan has quit [Quit: Connection closed for inactivity]