6 ms·
- Not-so-great documentation. - Lengthy learning curve. - Not concerned with performance at all (can be a nightmare on mobile devices with low RAM). - Google
by usingpond 12y ago
- Not-so-great documentation.
- Lengthy learning curve.
- Not concerned with performance at all (can be a nightmare on mobile devices with low RAM).
- Google's history of throwing away and/or deprecating projects, (see Angular v1).
- I still have yet to see a Google website using Angular in any large capacity.
- Ecosystem lock-in. It tries to do a LOT of stuff, and you generally need to be doing all these things the Angular Way™.
- adamnemecek 12y ago> - Not concerned with performance what are the performance issues with TS?
- usingpond 12y agoNo, that's Angular that has the perf issues.
- adamnemecek 12y agoOh, I see. NVM then.
- jonesetc 12y agoI think this was a jab at Angular, not TS.
- bceagle 12y ago> Not concerned with performance at all I would strongly disagree. Watch this link to when Igor talks about Angular performance. https://www.youtube.com/watch?v=QHulaj5ZxbI&t=35m30s https://www.youtube.com/watch?v=QHulaj5ZxbI&t=35m30s
- robmcm 12y ago> I still have yet to see a Google website using Angular in any large capacity. Angular is not intended for typical "websites". It's for replacing what would previously have been desktop CRUD applications. Google use it extensively for internal tooling. It's also worth remembering that most public facing Google applications have been around for years, decades even. It would take a long time to replace one of these with Angular, even if there was a desire to do so.
- noobhater1000 12y agoSo where is the example of why I would want to use Angular? And if it's so great Google would have transferred some of their websites over to it. I see no example of Angular being some awesome framework that inspires me to use it.