szines

In terms of WebStorm, dont forget to exclude tmp folders and other generated, transpiled content folder to exclude from indexing, otherweise it will be always busy. :)

There is a nice tutorial which is about building huge application in Ember.js. Totally free and easy to follow. Check it out. http://yoember.com

Probably the best bet nowadays is Ember.js. You don't have to reinvent the wheel. It works out of the box and you can focus on your application. And no crap. Matured, robust, scalable, faster than others (the new Glimmer 2 is 3x times faster than React...), huge add-on ecosystem. Easy to learn, great tutorials and guide. No more problem at all. ;)

Yep, you are right. There was Ember.State and Ember.StateManager, but it was extracted from the final v1.0.0. Instead of having one universal State Manager, router, views, etc got they own.

However, this universal State Manager is still exist and you can add to your project. https://github.com/emberjs/ember-states

After spending 15 minutes in the source code, it is ready to use... for example, it is brilliant to manage states in a component tree, where the original router would overkill.

Yep. Ember is the best solution out there at the moment. There is a trend, that silently more and more serious dev team switching to Ember. Ember never had hype period. It works and it is really matured. With Ember you can focus to your product and you don't worry any more about tools. I think most of the Ember dev is just smiling when they see these debates, because for us everything work and we ship day by day with a very high level of developer happiness. :)

I’ve been using ES6 modules in Ember.js development for two years now. Using Ember CLI is simplified down the dev process extreamly. The whole dev app development is so simple and fun with Ember. I don’t understand why people cry about it, the solution is exist, they should just use it. Thats all.

Yep, great choice. I've just updated my free Ember.js tutorial, if you would like to learn more about it: http://yoember.com

I'm playing with the server side rendering nowadays, and it is promising. It will be easy to use and nicely integrated with the whole ecosystem.

This blog post is not short, but you can get a view, what is the core team's plan for the next couple of weeks, and how the framework evolve further this year. http://emberjs.com/blog/2016/01/23/core-team-face-to-face-ja...

Yes, you right, if you need only a simple component, React is almost the fastest.

However, if you have a couple of level deep nested structure, nested components, React perform very badly. Probably Ember.js will never be the fastest framework on todo list performance test. However in complex application, it is fast, or maybe faster than any other solution. The Glimmer Engine 2 is on the way, will be released in a couple of weeks with backward compatibility. So if you built an Ember.js app before, it will enjoy this performance boost as well. And improving performance will never stop, so it is just getting better, meanwhile the developer happiness is on the top, thanks to Ember ecosystem, the add-ons, the Ember-CLI, etc...

In most of the projects the importance of the speed of rendering a tiny component is insignificant comparing to the speed of the network, or to the importance of the management of model/serialisers/adapters, or to dealing with app router/services, or to the importance of testing and deployment.

Ember.js project's main goal is providing a complex solution, where the developer has to focus only to ship a product, building features and release it. Ember achieved this goal more than a year ago, the whole framework is matured, more production and corporate ready than any other solution out there at the moment.

A great presentation about how intercom.io can ship fast thanks for Ember.js: https://www.youtube.com/watch?v=fVwDuMGVhYY&sns=tw

Nice comparison of renderers: https://auth0.com/blog/2015/11/20/face-off-virtual-dom-vs-in...

For the same reason I switched to Ember.js. I prefer the more opinionated way, the conventions. It looks to me, this repo try to provide some structure, but this is only one from the other 25 projects which do the same. The development effort is so fragmented. Should focus only one good react based framework. Luckily Ember.js is already implemented the good parts from React and from the Flux concept, stable, production ready, huge community. When you work with Ember, you dont feel that "fatigue" bullshit, because it is just disappeared. ;)

Ember.js 1.0 was release in 2013. The udpate pipeline strictly follows the Semantic Versioning standard. There is a new minor version every six week. Backward compatibility is extremely important. Ember.js 2 was released middle of last year, the transition from v1 to v2 was super smooth. Big startups and corporates (like financial companies) are migrating to Ember.js, because of the stability and because of the opinionated, convention over configuration features. An Ember developer can jump in someone else Ember project immediately, because most of the Ember.js app follows the same principals and rules. This is a good video about how Intercom.io was able to ship new features much faster and more often because of they switched to Ember: https://www.youtube.com/watch?v=fVwDuMGVhYY&sns=tw

I read this article about Meteor recently. https://www.discovermeteor.com/blog/the-state-of-meteor-part... Looks, they have to find a new way. It is kind of the same story as happened with Angular, the Angular 1 was a cul-de-sac and they had to build up a totally new framework from scratch.

Meanwhile Ember adapts the best solutions all the time. Ember begun to use ES6 almost two years ago. Implemented React inspired view layer a year ago. Server side rendering just released a couple of weeks ago. Ember-cli stable version is released a year ago, which is so good, that Angular 2 would like a similar cli tool, and of course Ember-cli team helps them. Hopefully Angular 2 will have a cli tool by middle of this year.

We could say, that Ember.js is at least 1 or maybe 2 years ahead of other javascript libraries or frameworks in more aspects at the moment.

Suggested pages: http://www.emberjs.com, http://www.ember-cli.com, http://yoember.com, https://guides.emberjs.com/v2.3.0/ http://www.emberjs.com/community

Here is a fresh report, which mirrors how serious the community behind this open source project: http://emberjs.com/blog/2016/01/23/core-team-face-to-face-ja...

Be careful, because if you start learning Ember.js, you will fall in love and you don't want to work with other javascript library any more. ;)

Ember 2 was released middle of last year and the transition was super smooth. Ember's update pipeline is strict and the backward compatibility is serious. Big startups and corporates are switching to Ember, because they want results... Luckily, we can say, at the moment Ember.js is at least 1 year, but more likely 2 years ahead of other js libraries and frameworks. The framework really matured, the best bet nowadays if someone plan to build larger frontend application.

Because Ember devs already found the best tool years ago and they are super productive. The community is huge and super active but they definitely totally ignore this "fatigue" bullshit... you know, if you found your love of your life, you don't go any more in the dance club to chase other boys/girls... ;)

Well written. Great post. Thanks for that.

"People can jump between Ember apps and be productive straight from the get-go. Another thing that blew my mind was that Ember encourages developers to write code in ES6 way and manage asynchrony with promises. I bet many JavaScript developers have only vaguely heard about these things as “The future of JavaScript”, while Ember developers are using it for quite some time, by default."

EmberJS renderer is so fast as React JS... Amazing and wow! Congratulation! https://www.youtube.com/watch?v=o12-90Dm-Qs&feature=youtu.be...