This is going to be long post, probably a ramble, about why I settled on Ember as the new age MV* framework I wanted to learn.
As an aside, during this time I was also migrating from ASP .NET Web Forms to ASP .NET MVC, experimenting with Django, Ruby on Rails, and various PHP MV* server side frameworks. This ushered me into a new future, that I could understand and grasp more easily than ASP .NET Web Forms.
I knew I could rule out Knockout, I really liked it, but it wasn’t a complete package. Backbone doesn’t provide enough structure. Angular was sweeping the dev communities that I was plugged in to, so I decided I would check it out. As I learned more about Angular, I found that there was not a lot of guidance to application structure, there was not a built-in router, and the use of data attributes just bothered me. Why do frameworks insist on messing with your HTML. I want clean HTML and I felt Angular didn’t give me that. Another struggle with Angular is the weird naming of things (Ember does it too), why name stuff after patterns, when the pattern doesn’t really fit. I questioned the descision to not go with Angular, but the recent news of 2.0 reassures me that I am glad that I didn’t. I breifly considered Durandal, but it was announced that Rob was going to Angular. I would consider it now that Rob is back.
So after all this searching I decided to finally pick up Ember. Rob Conery’s posts about Ember scared me off initially, and finally Rob put out a post that ran through the terminology used by Ember into terms that I could understand which helped. I then started working through a couple tutorials to see how I liked their philosophy. I will say the first few weeks were really trying my patience, but once it started to click, I realized that my style really fits well with Ember. So that is kind of why I am embracing Ember. Clearly, with my recent flurry of posts, it would be obvious that Ember and I mesh well.
Thank for reading