31 karma · joined September 30, 2010
The problem is just that you're nearly a year too late.
- yep angular has flaws (which framework doesn't?)
- ya, it does dirty checking and yes, that might have perf implications if used the wrong way. But hey, 6 years ago when Angular was created it was a revolutionizing idea, and still holds today. Also, at that time no Objecte.observe existed, nor did SPAs really (well..GWT was kinda the solution at that time). But, did u check what they're doing in Angular 2? Heard about RxJS and stuff?
- DI: strange syntax techniques to work around minifiers? You don't really use those, do u? heard about ngAnnotate?
- Oh...AMD, UMD etc...do not dependency injection. And yes, agree, DI together in combination with AMD/UMD/... creates confusion with newbie frontend developers
- Then: Angular 2 is already live on GitHub, for a while; has even it's own webpage online
- and for god's sake..Angular 2 is compatible with Angular 1...read their blog posts, their Tweets, weekly meetup notes and design docs (all openely available on GDocs)
- oh..and there are even some rumors server-side rendering will be possible in ng 2
I like ur blog, but if you go and rant, please check the latest status, inform yourself, then rant. Nothing against critics, they foster discussion, but only if made properly.
Thx
So far I didn't use it, but will definitely try it out.
But I generally like how it approaches policies, data store abstraction and seemless REST http and real-time socket routing. Awesome stuff.
However, I wonder how long it'll take till we can actively use them in production code...