@Hao wrote:
I would love to hear your opinion
- Experience: My experince with Ember(months) better than Angular (days) - Terminology: Angular( Routes, Component, Services, DI, Providers, Directives, Pipes, Services). Ember (Routes, Model, Components, Data Store) - TypeScript(Angular) very Java, Ember is less "java" (OOP) - Routing (angluar: ember: ) - Data on the client side( angluar: self-managing, Ember: data store) - Framework flexiblity(anglar > ember) by OO abstractiion and de-coupling while Ember has wrap it up - Framework easiness( anglar < ember): ember has built in Route/Model/Serializer/Store - Component (same) - Service (DI feature, same) - History( Ember (2 years), Angular1(>2yrs)(Angular2 ~ 1 months) - Sponsor Ember(Apple ex-staff), Angular(Google) - Cross platfrom(Native app) support ( both have it. With abstraction leve. A seems > E.) - Examples(many, stackoverflow, forum) - Open Source (ember > Angualr)Feeling in my guts: Even Ember is better. Angular will win. Because:
Angular is again driven by Google scheme to take over the market to make it suitable for all platform and Java developer friendly. The more OO/Java you are, the easier it is for you. I am not Java develper so I don't see much of a benefit at all and it feels not natrual even because I am more functional than OO. Also, they seems trying to solve Asynchonocy events cancelation/exception handling problem by reying on DI/Serice/Provider patterna and reactive styles. I don't see there is such a problem yet( maybe I am not experienced enough) when it comes to single page app development because ember has very much minimize that problem by Ember Data store (in my opinion) to load data into the client side and cache it into a store, only make remte request when you have to.
Posts: 1
Participants: 1