||[Oct. 10th, 2016|10:00 pm]
- I literally had to buy a React+d3.js ebook to figure out how to get all this crap set up. (the book is pretty good, by the by)
- The book recommends starting from a particular git repository. To clone that on my linux machine I had to set up some SSH key stuff, which seemed like overkill. (why do I need to do that for anonymous access?)
- To set it up, it downloads something on the order of 300 packages through npm. I wish I were exaggerating.
- React now recommends you use ES6 instead of calling React.createClass(), and there are some niceties there. But there also some stupid gotchas, like the fact that you have to call
.bind(this) on every method for it to be able to access
- For some reason I'm not able to debug with Firefox's debugging tools. (luckily Edge seems to work well)
- I wasted an hour because the new fancy
fetch standard (not supported in some versions of IE so you need a polyfill) has a method called
text() that returns the text of the response. Wait, no, it actually returns a promise that has the text of the response. I never realized how much I liked C#'s standard of ending asynchronous methods with "Async" before...