Echo JS 0.11.0

Yeah, I was really interested in Aphrodite, but react-jss just seems slightly better in terms of a solution.  It renders to style tag(s), so you can do media queries, and you can invert nesting similar to sass/less, so it's not bad.. remembering to quote css properties is the only hard part (similar to inline)... you get classes to set on your rendered components, similar to aphrodite (iirc), and it goes well enough.

Very cool... would love to see a jest version of this...

I've either gone with Sass (via webpack/require) per component, or with JSS (my preference lately)... react-jss works pretty well, and I can always start with inline, change to jss as I go.  Some things are a bit awkward starting out, but it's easier to share configs and common settings with JSS.  My only complaint is the library is a little heavy.

I haven't not used babel in some while now... even for smaller, personal bits... though not always via webpack.

No react-jss

My favorite, and really useful for batch processing scripts, is `--expose-gc` which allows you to use `global.gc()` in your processing script after each item (or N items), keeping your total memory use lower.  It's not a good thing for service processes (generally), but for long-running workers, can keep you from experiencing large GCs in the middle of the run, or from inflating the memory use on a system that's shared for other processing scripts.

Didn't watch the whole thing... seriously, the presumtion is that Angular was ever great to begin with.  Every time I've used Angular, I've come across so many odd WTF moments, I regretted even using ng in the first place...  2+ is better, but still not "good".  It's too prescriptive in the first place, fights upstream conventions and the DSL for templating is painful.  Having to "inject" what's already required in is kind of weird too (ng2+).

In general, just not enough of a fan to care anymore...  If I can do React, I will.. if it's better served with simple forms/submit + jQuery, I'll do that.  but ng is out of my life.  I'd rather do web components, vue, polymer etc over angular of any brand, and React over all of them.  That's just my POV.

Another issue is there are still upcoming features via babel that are useful but not in the browsers yet... and even then, you need a build process to support older browsers anyway (IE11 will be around for a few more years still).

Seeing exploits like this is just wild in my mind.  Sometimes I read things things and think, man, I get how it worked, but I just never have the mind to do things like this... The only times I'm creative working around things is when I need to be.

I'm finding that react-router v4 is perfectly serviceable... only really needed to add a single listener to dispatch a route update into my store... since the router handles the routes anyway.