4 ms·
FTA: >When evaluating Ember, We were excited that with ember-data there were established patterns for how to do things — even if some of those patterns felt a l
by duderific 10y ago
FTA:
>When evaluating Ember, We were excited that with ember-data there were established patterns for how to do things — even if some of those patterns felt a little outdated.
Could you elaborate a bit on how the ember-data patterns felt outdated?
- jessepollak 10y agoAbsolutely! I would say that with Ember + ember-data, the framework conforms to a pattern where data is represented as models on the frontend, which can be updated and persisted to the server. These updates happen through a CRUD / REST API (in our case we conform to JSONAPI) and are generally triggered in a controller (or a route that contains logic and acts similar to a controller in a traditional MVC framework). In the React ecosystem, I think there's been a pretty stark departure from that general pattern with things like redux and GraphQL, so while we love it, compared to what we'd been using , it felt a little behind. Does that make sense?
- duderific 10y agoYes it does, thanks!