[CircleJerk]

My english is awful, I was trying to say it's not really a SPA that I'm making. I want to keep the routing mainly on my back-end and only do ajax calls to my API where needed. But if it's not another alpha-state component I would love to have the added possibility of using one or two extra routes on the JS side. It's just that checking the most popular repos and reading things like these is awful: "We are currently working hard on some major API changes for version 1.0."

Is like "mini-SPA's" on a few places that deal with too many data sources and would be a pain to make my users change screens.

I really enjoyed doing "one way binding" and some ideas around React though.

[hliyan]

> I want to keep the routing mainly on my back-end and only do ajax calls to my API where needed.

I'm not trying to push React (I'm still evaluating it myself), but that sounds like just the job for React components?

[CircleJerk]

Check my other reply. React is great but I think you need to buy the entire stack since one thing leads to the other. "I'm already using JSX so why not add just this one more babel line and get free ES6. It's the last thing I'll add, I swear"

[hliyan]

I thought React was designed specifically so you won't have to buy into the entire stack (unlike Ember and friends). I've used React components without ES6, using plain old jQuery and AJAX calls during component mount (and nothing else). I didn't feel any particular temptation to add more things. Okay I'm lying :) . It's tempting, but it's possible to do without.

[CircleJerk]

You weren't using JSX?

[hliyan]

I did. It's part of React proper and merely syntactic sugar over React.DOM calls. You can use React.DOM directly, but it doesn't really change your level of investment in the 'stack', IMO.