Beautiful site -- lovely to see open source design in action.<p>It's fun to look at this new site in the context of the progression in the various iterations of the SproutCore saga over the years:<p><a href="http://web.archive.org/web/20081003190606/http://www.sproutcore.com/" rel="nofollow">http://web.archive.org/web/20081003190606/http://www.sproutc...</a><p><a href="http://web.archive.org/web/20110211051741/http://www.sproutcore.com/" rel="nofollow">http://web.archive.org/web/20110211051741/http://www.sproutc...</a><p><a href="http://sproutcore.com/" rel="nofollow">http://sproutcore.com/</a><p><a href="http://emberjs.com/" rel="nofollow">http://emberjs.com/</a>
I'm sad that the on-site docs are still inferior compared to the in-code comment docs. For example, the on-site docs hardly mention the built-in state manager, but they're very thoroughly documented in the code [1]. Many people (myself included) people will usually resort to searching Google before looking in the code when trying to figure out how to do something.<p>Ember team, any insight as to what's being done to rectify this, or why this is?<p>[1] <a href="https://github.com/emberjs/ember.js/blob/master/packages/ember-states/lib/state_manager.js#L5" rel="nofollow">https://github.com/emberjs/ember.js/blob/master/packages/emb...</a>
Can someone describe emberjs in one line?<p>(Their description of a <i>framework for making ambitious web apps</i> is a bit vague imho and i don't want to spend 15 mins reading docs about something that may not be of any use to me at all.)
The documentation is underwhelming, from a get-up-and-running POV ... protip for authors of new libraries etc. I should be able to cut and paste your code and have it just work right away.<p>If you don't add<p>var MyApp = Em.Application.create();<p>to the examples in the docs page the code simply won't work.
It's a bit odd that the main example on the home page references an object called DS on 8 of 10 lines, but DS is never referenced elsewhere in the documentation.<p>I know from prior exploration at their github account that DS stands for "data store" but I still think it's pretty weird that searching for "DS" on the docs page brings up nothing.
Woo! I was at first a bit disappointed to see only two guides - good thing I checked out the docs.<p>Hopefully now the docs around EmberJS can stabilize and really take off.
On a more personal note, it would be great if someone could compare this with meteor.js (which recently got featured on HN)? I mean a brief comparison would be really great..without having to dig up the docs in detail..
On a more personal note, it would be great if someone could compare this with spine.js (which recently got featured on HN)? I mean a brief comparison would be really great..without having to dig up the docs in detail..
What makes me sad about js client-side frameworks and Ember.js in particular is that they are still only client-side. Nevermind the code duplication, but the bare fact that I have to actually think about how to construct my server so that it works with Ember.js. The reason why people hooked up on Rails so quickly is because it solved all of their problems, not just one. Novices are not going to try Ember.js just because it works on the client, while having no idea about the server-side.
Comparing it to Backbone, feels to me that Ember uses a notation that is closer to what I already know about Javascript, for example all the object methods and prototype class emulation. I was going through the API and everything seemed like it made sense right away. The only thing I wish the site had is more examples with bi-directional bindings.
This <i>seems</i> cool, but as someone who has never seen emberjs before, the "js" part of the "getting started with emberjs is easy" was not very clear.<p>It's clearly some model/controller logic, but what is ArrayController? And how is the view chosen?<p>Just some feedback from fresh eyes
We just started playing with this, it seems like a great alternative to backbone for those who want a bit more of the common stuff done for you (esp data binding).<p>Backbone is a great starting point if you have strong opinions and want to own it from the ground up.<p>Just my $0.01
Is the 42k min+gzip all in? Or are jQuery and Handlebars still separate downloads?<p>The example on the front page shows code from ember-data. Is that a separate, additional download too?
How mature are the ember community's various supporting libraries and boilerplate builds? This kind of bothered me:<p><a href="http://emberjs.com/documentation/#toc_getting-started" rel="nofollow">http://emberjs.com/documentation/#toc_getting-started</a>
>> <i></i>If your needs are simple or you're interested in just playing around, you can download the Ember.js Starter Kit. The Starter Kit is based on HTML5 Boilerplate and does not require any build tools or other dependencies...For larger apps, you may want to consider using Ruby on Rails. Rails helps you manage your source code and other assets, while also providing the REST API that your application will talk to.<i></i><p>(not saying that backbone et. al have better boilerplate builders. Just that hopefully there's a medium ground between HTML5 templates and RoR, the latter which I hope to mostly avoid through the use of JS frameworks)