4 ms·
That's a valid complaint. I wrote it with a Rails backend because that's a pretty popular backend choice for Ember, and they work together well. Perhaps I can
by hpvic03 12y ago
That's a valid complaint. I wrote it with a Rails backend because that's a pretty popular backend choice for Ember, and they work together well.
Perhaps I can just extract out the Ember portion -- It should still be applicable regardless of the backend.
- endemic 12y agoMaybe stub out the backend with an Express app? Express seems simple enough that even if you're not familiar with it, you can still understand what it's trying to do.
- TheBrockEllis 12y agoAnd you'd keep most of the code in javascript so new comers wouldn't get "culture shock" by having to learn completely new syntax. +1
- Nemcue 12y agoDo you even /need/ a backend though? It would be much simpler if you keep it entirely client side, using something like Pretender (https://github.com/trek/pretender https://github.com/trek/pretender).
- hpvic03 12y agoTo persist data you'll want a backend. That's a fairly important piece of any application which is why I included it in the tutorial. You could ignore the Rails parts of the tutorial and create your own backend.
- pyre 12y agoPersist across clients, maybe, but it's also possible to use localStorage to persist data on a single client.
- TheBrockEllis 12y agoYou could also use something like Firebase as a datastore that could persist across multiple clients but also be implemented in javascript.
- wasd 12y agoWould you consider Parse/Firebase?