David Chang

Actually I am not quite familiar with the Observable code base, so here is a first scan of discovery. So we are going to deprecate the following APIs, 1. `param...

Now I got the point. And I think this is related to https://github.com/reactrb/reactrb/issues/136, right? So instead of deprecating this, maybe we could extract this as a separate module first, 1....

Haven't actually got a chance to try out Observable state provided, but other than redux, reactjs community is also using [MobX](https://github.com/mobxjs/mobx) which provide observable state management by a different way....

I am planing to work on a version of `State` which is decoupled with `this.state` managed by ReactJS. This may give a better chance for us to extract this out...

I think there is no reason to stop us from adding `empty?` to `React::Children`

Ruby's `Enumerable` doesn't provide `empty?` method, it got something similar which is `any?`.

I am trying to reproduce the issue, but it seems like passing a `Date` as foo won't raise any exception. Would love to help if @fzingg could provide more information....

@fzingg , thanks for updating the information. Does a exception like the following help? ``` Exception raised while rendering #: Instead of String or React::Element, a Time object was returned...

Hi, I've go through the features you proposed, for > A copy of the current state is kept, so it can be read during events. > ReactJS does not guarantee...

I think caching state for getter is a great idea, would you mind make a separate request for this feature? > The ReactJS convention seems to be the capitalize component...