12 ms·

I am pretty sure that TypeScript just adds type safety and is optional. I don't see this as a huge negative and I actually see this as a positive. Just curious

by dmarg 12y ago

I am pretty sure that TypeScript just adds type safety and is optional. I don't see this as a huge negative and I actually see this as a positive. Just curious, what and why are all your reasons to move away from Angular?

deleted 12y ago
[deleted]
WalterSear 12y ago
- Breaking changes - Obtuse, verbose, non-performant code - Did I mention breaking changes?
- agumonkey 12y ago
  On the other side, the ember guys released a drop-in update.
- EugeneOZ 12y ago
  Pretty performant, see notes: http://t.co/gyBhc5jWzI http://t.co/gyBhc5jWzI (or streaming video right now)
- jhall1468 12y ago
  Because progress sucks. I still don't see why we don't continue using IE 6.
  - WalterSear 12y ago
    Progress is great. IMHO, Angular isn't progress, and neither is painting yourself into a corner.
    - jhall1468 12y ago
      According to you it isn't. And that's the fundamental problem here... opinions are like assholes, everyone has one and yours certainly isn't worth more than mine.
      - WalterSear 12y ago
        I don't know about that. I contributed to protractor and have worked with members of the Angular team in the past. Opinions maybe useless, but some opinions are more useless than others.
shubhamjain 12y ago
If type safety was the issue, couldn't they have tried Facebook's Flow[1] which believe would have reduced the technical overhead by large? [1]: http://flowtype.org/ http://flowtype.org/
- Bahamut 12y ago
  TypeScript has been around longer, and is more widely used. FWIW, the Angular team mentioned they talked with the Flow team - not sure what that will mean in the near term, but I get the impression that efforts might be in progress to unify the different libraries' efforts.
- ahoge 12y ago
  Flow doesn't work on Windows yet. Atom seems to be the only editor which supports it. That plugin had its 2nd release just 3 days ago.
  - zghst 12y ago
    If I can get Flow to work in vim, I am sure it works in more than just Atom
    - ahoge 12y ago
      Define "get to work". I mean something like this: https://atom.io/packages/ide-flow https://atom.io/packages/ide-flow Tool-tips, call-tips, auto-complete, type checking, and so forth. The kind of stuff you get with TypeScript or Dart.
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 ago
    No, that's Angular that has the perf issues.
    - adamnemecek 12y ago
      Oh, I see. NVM then.
  - jonesetc 12y ago
    I 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.

by dmarg 12y ago

deleted 12y ago

[deleted]

WalterSear 12y ago

- Breaking changes - Obtuse, verbose, non-performant code - Did I mention breaking changes?

agumonkey 12y ago
On the other side, the ember guys released a drop-in update.
EugeneOZ 12y ago
Pretty performant, see notes: http://t.co/gyBhc5jWzI http://t.co/gyBhc5jWzI (or streaming video right now)
jhall1468 12y ago
Because progress sucks. I still don't see why we don't continue using IE 6.
- WalterSear 12y ago
  Progress is great. IMHO, Angular isn't progress, and neither is painting yourself into a corner.
  - jhall1468 12y ago
    According to you it isn't. And that's the fundamental problem here... opinions are like assholes, everyone has one and yours certainly isn't worth more than mine.
    - WalterSear 12y ago
      I don't know about that. I contributed to protractor and have worked with members of the Angular team in the past. Opinions maybe useless, but some opinions are more useless than others.

shubhamjain 12y ago

If type safety was the issue, couldn't they have tried Facebook's Flow[1] which believe would have reduced the technical overhead by large? [1]: http://flowtype.org/ http://flowtype.org/

Bahamut 12y ago
TypeScript has been around longer, and is more widely used. FWIW, the Angular team mentioned they talked with the Flow team - not sure what that will mean in the near term, but I get the impression that efforts might be in progress to unify the different libraries' efforts.
ahoge 12y ago
Flow doesn't work on Windows yet. Atom seems to be the only editor which supports it. That plugin had its 2nd release just 3 days ago.
- zghst 12y ago
  If I can get Flow to work in vim, I am sure it works in more than just Atom
  - ahoge 12y ago
    Define "get to work". I mean something like this: https://atom.io/packages/ide-flow https://atom.io/packages/ide-flow Tool-tips, call-tips, auto-complete, type checking, and so forth. The kind of stuff you get with TypeScript or Dart.

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 ago
  No, that's Angular that has the perf issues.
  - adamnemecek 12y ago
    Oh, I see. NVM then.
- jonesetc 12y ago
  I 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.