Lady, EVOLVED 
there is something really horrifying happening in the glitchsoc frontend codebase
arrow functions which have `this.props` in their body
how does this site… function
@Lady oh my lord
@aescling legitimately i think this entire frontend is built on top of a jenga tower of outdated babel transforms which can never be updated
@aescling oh i figured it out and it’s cursed
@aescling i liked it better when i didn’t know
@Lady why is that remarkable. idgi
@alyssa it's very cursed imo for arrow functions to refer to `this` when they don't appear inside a different non-arrow function whose `this` they are inheriting, but this is apparently normal for React
@aescling @alyssa no, the arrow functions are being defined using = inside a class declaration, so the context is the constructed instance (instance fields are defined after the call to `super()` in the constructor iirc)
like
class Blah extends React.Component {
yep = () => {}
}
is doing
class Blah extends React.Component {
constructor() {
super()
this.yep = () => {}
}
}
god it doesn’t support `??` how outdated is this stack