Echo JS 0.11.0

I've read most of them...  I'm hoping that at least one of them sees a really good ES2017 update including all the added goodness of today's JS.  Possibly including a babel/webpack setup walkthrough.

It's not great for those learning JS, but would be very useful to those to whome JS is a second language... hell there's a great name for a JS book, "JavaScript As A Second Language" (JSL)

Like many of these types of articles, it really feels like most of the ng2 v react articles are written by people who are mostly used to angular and moving towards 2, while looking into react.

As to DI.. really, the context that gets passed down is the convention for this, as needed.  It's how the react-redux injects the state and actions from the store, how router passes itself down to routes/links, and how tools like material-ui access theming information.

Beyond those cases, you really shouldn't *need* DI, there are tools like rewire for babel, and others (proxyquire, etc) that provide injection for testing purposes.

React + Redux + fetch, are pretty much all you need in terms of "framework", there's also webpack, babel, and some css solution (react-jss, sass-loader, or similar) ymmv.

Blog Spam

It's funny, but the specification for JS says that it's supposed to use UCS16/UTF16 for it's internal string representation.  This means that anything over 16 bits uses a set...  I kind of wish they'd just switched to UTF-8 around EcmaScript3, before it was too big of an issue, now we're effectively stuck with it.

It would still have interesting lengths, but would at least be slightly more predictable... String's .normalize is an example of all that is wrong in this space... it's really wild.

It's also really important to be aware of this stuff and normalize before doing password hashing for your applications.

It's a matter of choice, for something like KendoUI, they could do like material-ui and plenty of others, and have a larger package, you can cherry pick individual components from.

Nice...

Nice...

One place where I will break from FP is with UI components... And that's mainly because the syntax is easier, and with React you can use PureComponent, where as render components aren't considered pure by the framework and re-evaluated on every pass.

That's more of an issue with React, not FP... but context binding is easier with OO, where control flows, and state mgt are easier (imho) with FP.

relatively nice little project...  would be nice if it supported/passed in yaml front matter.

I like this...  A lot of other control flows make things more complicated to use, while this is just a building block that can be used on top of redux-thunk.