Don't forget Google Wave -shudders-
I'm so annoyed by Microsoft touting their leading the edge of ES6 feature support. Especially with statements such as:
> last week’s Windows Insider Preview build 14342 brings more ES6 capabilities including modules, default parameters, and destructuring
With the exception of modules, Chrome and FF have supported the more frequently used ES2015 features like destructuring and default params for quite a while now.
This comment leaves a sour taste in my mouth. Regardless of how he handled the situation (not well), I'm uncomfortable with what happened. Kik were quick to mention legal ramifications. Azer lost a project.
On top of this - it doesn't serve any benefit to badmouth individuals like this. It reads a lot like "preachy developer whining about some other preachy developer".
Hey - looks awesome! Was wondering why you import `object-assign` rather than using `Object.assign()`?
edit: Derp. I read more of the project. No polyfill. My bad :/
I'm hoping I'm not the 'fool' in this sentence. It's hard to extrapolate POV from your comment.
Preach it, preacher man! I can't count on my hands and toes how often I have to explain this (and have actually been forced to justify why I used `const`; which the person grilling me didn't understand is a block scoped variable, not global like he believed).
Cool, thanks for the clarification.
I guess I should read a bit of the Rx API docs, but doesn't seem far off Bacon with `combineTemplate`; which from memory returns a curried function to end any streams. Someone correct me if I'm wrong.
Perhaps you're right - but the trend doesn't necessarily account for all use cases.
Assuming the OP is only modifying the components internal state (which has no bearing on the application state), I'd be all for it.
Hey, thanks for the share. Where I haven't used Rx per se, I used Bacon extensively at my last gig.
Rx is a module, and you're merging `plus$` and `minus$` to 'Rx.Observable' - is there an issue of having these bindings persist when the React component unmounts? What would be the best practice for tidying up in `componentWillUnmount`?
Moved to http://airbnb.io/enzyme/ as far as I can tell.