4 ms·

Since the developers are here in this thread- I'm curious where this goes from here. I'm an Ember developer, but sometimes Ember's heavyweight attitude isn't ne

Since the developers are here in this thread- I'm curious where this goes from here. I'm an Ember developer, but sometimes Ember's heavyweight attitude isn't needed for a project, and I see React as the natural direction to go when I want something smaller. Seeing something like this, and the strength of having developer tools like Ember Inspector or React DevTools, is just going to make frontend development so much easier.

Cshelton 11y ago
Once you do web development the "react way", you'll probably drop Ember for every project and stick with React. Just saying. I've probably built over a thousand React components at this point. I've used all the other frameworks, knockout, Angular 1.x, ember. React is by far the better way to do things as of now.
- quaunaut 11y ago
  Personally, I'm not as confident. I spent a week doing a lot of React projects, and while it's nice, it is what it is- a view layer. When interacting with a complex web of routes, models, components, and templates, I have found Ember to be similar to Rails in terms of expressiveness and speed of development. Then again, I don't know a lot of the tools that people use to solve these problems in React- the most I ever encountered was having to do most things manually, but having page layout managed by React. I was still managing my M and C. What do you usually use to ease the work there?
  - k__ 11y ago
    Most people who say they use React usually don't use it stand-alone. When I say that I use React it includes the whole client-side stack. React, react-router (inspired by the Ember router), Redux, react-bootstrap and newforms. This is a bit like using Ember, Ember-Data, Bootstrap and ember-forms.
    - quaunaut 11y ago
      Thanks! I'll give it another shot, using those exact tools. Is there any guide out there for the usual application structure?
  - coldtea 11y ago
    >I spent a week doing a lot of React projects That's not much -- and all the projects are probably toy projects, to fit all of them in a week's span. >while it's nice, it is what it is- a view layer. Sure, that's why you use Reflux, Redut and some other Flux architecture helper to frame your code, ReactRouter, etc.
    - why-el 11y ago
      Any idea who Reflux plays with a non-javascript backend such as Rails or Django?
      - lobster_johnson 11y ago
        Sure. The Flux-derived frameworks (such as Reflux) don't actually care about what your backend is -- they only deal with the internal data flow of your app. I haven't used Reflux, but I am pretty sure you have to implement the backend calls (AJAX or whatever) yourself.
      - coldtea 11y ago
        Can't really tell, as I've never played with client/backend side helpers (for AJAX etc), always kelp my backend independent.

Cshelton 11y ago

Once you do web development the "react way", you'll probably drop Ember for every project and stick with React. Just saying. I've probably built over a thousand React components at this point. I've used all the other frameworks, knockout, Angular 1.x, ember. React is by far the better way to do things as of now.

quaunaut 11y ago
Personally, I'm not as confident. I spent a week doing a lot of React projects, and while it's nice, it is what it is- a view layer. When interacting with a complex web of routes, models, components, and templates, I have found Ember to be similar to Rails in terms of expressiveness and speed of development. Then again, I don't know a lot of the tools that people use to solve these problems in React- the most I ever encountered was having to do most things manually, but having page layout managed by React. I was still managing my M and C. What do you usually use to ease the work there?
- k__ 11y ago
  Most people who say they use React usually don't use it stand-alone. When I say that I use React it includes the whole client-side stack. React, react-router (inspired by the Ember router), Redux, react-bootstrap and newforms. This is a bit like using Ember, Ember-Data, Bootstrap and ember-forms.
  - quaunaut 11y ago
    Thanks! I'll give it another shot, using those exact tools. Is there any guide out there for the usual application structure?
- coldtea 11y ago
  >I spent a week doing a lot of React projects That's not much -- and all the projects are probably toy projects, to fit all of them in a week's span. >while it's nice, it is what it is- a view layer. Sure, that's why you use Reflux, Redut and some other Flux architecture helper to frame your code, ReactRouter, etc.
  - why-el 11y ago
    Any idea who Reflux plays with a non-javascript backend such as Rails or Django?
    - lobster_johnson 11y ago
      Sure. The Flux-derived frameworks (such as Reflux) don't actually care about what your backend is -- they only deal with the internal data flow of your app. I haven't used Reflux, but I am pretty sure you have to implement the backend calls (AJAX or whatever) yourself.
    - coldtea 11y ago
      Can't really tell, as I've never played with client/backend side helpers (for AJAX etc), always kelp my backend independent.