4 ms·
A lot of rails devs I know have switched to ember.js [1], because it's also a framework based on conventions rather than having a million third-party plugins th
by cookiengineer 3y ago
A lot of rails devs I know have switched to ember.js [1], because it's also a framework based on conventions rather than having a million third-party plugins that break all the time.
Architecture-wise I really like the ember-data approach because it allows a lot of automations when it comes to left join/right joins of datasets, with an integrated mockup server etc.
But it's not as cool as the other ones I guess, because it just works too well enough!?
[1] https://emberjs.com/ https://emberjs.com/
- tonyedgecombe 3y agoI thought Ember was a front end framework or am I missing something?
- cookiengineer 3y agoThe idea behind ember-data [2] is that the models and their relationships are defined on the frontend side, which implies that the models are the single source of truth for both the frontend and the backend, including the APIs themselves. Ember adheres to json api specification, but there is lots of adapters for other database query languageds and/or storage types [1] As I said in my previous post, it's a framework based on conventions, so it'd a batteries-included approach to both frontend and backend. [1] https://emberobserver.com/categories/ember-data-adapters https://emberobserver.com/categories/ember-data-adapters [2] https://guides.emberjs.com/release/models/ https://guides.emberjs.com/release/models/