I've been keeping an eye out for a project on which to use Ember. Unfortunately, I've been in that exact mode for literally years. I already trust that it's solid stuff from having learned a load about software development from Yehuda back in the jQuery days.
Three or four times I've been about to pull the trigger and every time the things that's stopped me is that when I go to look for a sample project to have a read of an actual app using it in anger it seems impossible to find one that meets my criteria: 1. Uses current version of Ember. 2. Uses idiomatic ember. 3. Big enough to not be a toy, ember-data, being the recommended way of doing things, I want to see how it's formatted.
Every time a look it seems like everyone is saying something along the lines of "Here's a good example project except it's N versions old." or "… except it doesn't use insert-feature-that-docs-heavily-recommend-using because that wasn't around when this project started" or "… it uses local storage in place of a database".
I've read the documentation end to end multiple times over the years. I'm not sure why that's not enough for me. I just assume I'll run into trouble and I'd like to see an application with routing, component composition, backend calls, and understand a bit about the recommended backend before diving in.
Three or four times I've been about to pull the trigger and every time the things that's stopped me is that when I go to look for a sample project to have a read of an actual app using it in anger it seems impossible to find one that meets my criteria: 1. Uses current version of Ember. 2. Uses idiomatic ember. 3. Big enough to not be a toy, ember-data, being the recommended way of doing things, I want to see how it's formatted.
Every time a look it seems like everyone is saying something along the lines of "Here's a good example project except it's N versions old." or "… except it doesn't use insert-feature-that-docs-heavily-recommend-using because that wasn't around when this project started" or "… it uses local storage in place of a database".
I've read the documentation end to end multiple times over the years. I'm not sure why that's not enough for me. I just assume I'll run into trouble and I'd like to see an application with routing, component composition, backend calls, and understand a bit about the recommended backend before diving in.