Lots of great views and suggestions here! Thank you all for those!
I will try to respond to the ones that I feel most valuable in my view.
Crushing the misconceptions that HTTP is as stateful as TCP in developers minds is difficult and takes a lot of effort.
While Ember.js and AnuglarJS is different enough, I don’t think that most developers new to the JS webapp game look at them as “two different types of tools”. They are, in fact, both tools to write SPAs in the browser, andt they both claim to be backend agnostic. They are similar enough that most developers new to both these tools wont be able to tell where the difference is.
Embercasts is a great idea, along with well written tutorials and books. Depending on who creates them, it might not be feasible in the long run for these to be made free of charge though. Creating good content takes a lot of work, and for most people that is time spent away from generating income. I definitely fall into the category of creating content for money with Ember.js in Action, and even though I’ve yet to actually make any income with that book, it will, once its published hopefully generate enough income in order to free up time to create more content. I think many are in the same position as me though, wanting to create good content, but finding that its hard to find enough time to do that properly on top of work and family.
Generating income from content vs creating content for free is also a chicken-and-egg kind of issue. You can’t make any income from a market until it grows large enough to support enough people willing to pay for good content. This means that increasing the market needs to initially start out with lots of free content.
I also agree that there is very little non-rails-centric Ember.js content out there. Rails and Node.js is the “cool” solutions to build stuff on these days, and thus this is where the content writers go to when writing their content. Having well written content that targets Java, .NET and PHP is critical in order to win over those developers. And those three market segments in the web-application scene are absolutely huge!
We also need to showcase what large webapps written with Ember.js is doing in order to keep their development smooth and on track. Show and explain why learning and adopting the strict MVC patterns is going to pay off in dividends once your app grows.
I think, that the fact that you MUST use MVC to the full extend even for small apps is both a strenght and a weakness with Ember.js. En even though the learning curve have gotten a lot less steep with Ember.js now automatically generating routes, controllers and views, the developer still needs to know that theory are in fact there.
Also a great visual prototyping tool is a good idea, but it is also a LOT of work. Look at the Cappuccino group. They used to have an awesome webapp that let you assemble apps, but now they use an XCode plugin and use Interface Builder instead. I don’t see that building such a tool is possible without some serious financial backing.
Also, the fact that some Ember.js books are resources is out of date is sad, but understandable. I’m glad I’ve held off with Ember.js in Action until Ember.js was stable. It wont come out until March, as Manning will spend a lot of time in production, getting everyting into the “Manning” style. That is the advantage of self publishing, you can publish early and often, where the advantage of going with a publisher is that the content will need to be properly proofed, as thousands of printed book will be printed and shipped to customers and bookstores (there’s no re-doing the print )
I am hopeful for the future. And as someone mentioned, Ember.js doesn’t really have to compete with Angular. The real competitors are JavaServer Faces, .NET Webforms and the various PHP server-side frameworks. This is truly where Ember.js’ market is, and we need to do out part to grab it!
That was my loooong resonse to all of your great commetns and suggestions As you can see, I like to write