21:02 <ec> anybody use Linux on the desktop and got a second to try something for me? I've spent all goddamn day banging my head against VMware and Linux Mint and apt-get and open-vm-tools and all I goddamn want is to run a few git commands

21:02 <ec> someone be lovely and try this for me on their machine? because my git checkout is failing on Travis, but only on the Linux workers, and I can't fucking figure out why

21:07 <ec> th'fuck kind of API is this

21:07 <ec> `const [loading, setLoading] = useState(true);`

21:07 <ec> @jfhbrook

22:09 <jfhbrook> ec: it's react hooks :) and yeah it's super whacky but I kinda like it

22:26 <jfhbrook> ec: the way they work is that useState has access to a closure where it tracks the state, and it depends on controlling the lifecycle of the component to know which component is active for any given hook (basically)

22:26 <jfhbrook> ec: but it's a replacement for the this.setState pattern, end of day

22:26 <jfhbrook> oh, but I can give your linux thing a shot later, I'm going home very soon

22:27 <ec> I don't know the this.setState pattern; I don't use React

22:30 <ec> jfhbrook: that'd be very nice, yes

22:30 <ec> having a linux nightmare today

22:45 <jfhbrook> ec: so the way react components work is *waves hands* react holds onto a tree of components and re-instantiates them when it decides it needs to re-render - and rendering in the first place is due to immutable "props" and highly mutable "state", but the way it manages state using the OG class API is that the React.Component class has a method called setState that you use instead of manually modifying self.state

22:45 <jfhbrook> so when you call self.setState() it triggers react to recalculate its virtual DOMitude or whatever

22:46 <jfhbrook> hooks are an alternate API that let you return a function rather than a Component with a render() method

22:46 <jfhbrook> but it's all the same shit, just a more clever/weird API

22:47 <jfhbrook> by "re-instantiate" for Components I actually meant re-render - for hooks it has to call the "component function" instead

22:47 <ec> lol k

22:47 <ec> react is all greek to me but whadduh I know

22:47 <jfhbrook> yeah, this is all new to me too

22:48 <jfhbrook> after years of "eventually" I decided that I wanted to make an App

22:48 <ec> people are all on about props at conferences and I just tune out until they get back to the good stuff :P

22:48 <jfhbrook> and now I have a little react app that I'm enjoying

22:48 <jfhbrook> react is decent

22:48 <jfhbrook> the community is kinda dumb and there is a *lot* of really dumb shit built around it, like react-router and redux and I mean realistically you need webpack and babel now too

22:49 <jfhbrook> total circus to get up and running

22:49 <jfhbrook> but once you have it going it's alright

22:49 <jfhbrook> if you wanna play w/ this try https://nextjs.org/learn/basics/getting-started

22:50 <jfhbrook> it's like a canned thing, made by the zeit team, pretty solid tutorial, easy to get dirty

22:50 <ec> lol

22:50 <ec> see what you just called a “circus” is the bit I understand and/or care about :P

22:50 <ec> know plenty about webpack etc; it’s just frontend that’s greek

22:54 <ljharb> jfhbrook: you need a bundler and a transpiler for modern web dev no matter your stack

23:04 <jfhbrook> yeah didn’t mean to imply different

23:15 <ljharb> (not that i like webpack)

23:39 <jfhbrook> oh man I can't figure out how to set up this API!