Mitch VanDuyn

Just added some more syntax sugar and noise reduction. you can now say `define_state :foo, :bar, baz: 12, blog: 17` `foo` and `bar` will be initialized to nil. `baz` will...

@weid03 The intention is to make the reading/writing state syntax simple, without changing the semantics. As far as writing goes, the implementation always writes through to the react hash, so...

I don't even think we need this for 0.9, if it get fixed before then great, if not, oh well.

1) Not sure what scope: :shared even means? Can you elucidate? 2) Not sure about MyComponent.state.foo. I've thought about it, and I'm unconvinced. For one thing its at odds with...

**optional vs. mandantory state declarations** My biggest hesitation is it is not "ruby" like. However I think we should go ahead and make enforce strict state declarations. You have pointed...

To be clear on the syntax: `:class` can be specified as either `class: value`, or just `:class` The `:initial` key must have a value. but if there is no `:initial`...

To answer some of the questions and clarify, and tell you where I think we are at: 1) I think we go with reactrb. Pros - simple, consistent, and better...

regarding case: Okay well I guess I should say it should be capitalized like a normal noun. In otherwords: "Why are you using reactrb?" answer: "Reactrb is really great that...

okay I think we have a plan: 1) Name will change to reactrb across the board including the gem. I think we all hate to give up the nicer react.rb,...

Okay so if I understand you @ajjahn, we make reactrb = 0.8.0 which = 0.7.41 + don't load JS, etc. All changes slated for 0.8 get added to 0.9... The...