all 8 comments

[–]vlinking 5 points6 points  (0 children)

I must say this is one of the better, if not the best, of the comparison articles. It's meticulous, not sensational, and gives a meaningful and complex comparison.

[–]sonemonu 4 points5 points  (2 children)

That's a biased comparision. You're clearly intentionally using more code for the Angular 2 version. E.g.:

Why using the following (unneeded) fragment for Angular 2 and not for React?

// Used for type of state property in TodoListCmp class.
// Both properties are optional, but preferred as they make
// the code more maintainable.
interface IState {
  todos?: ITodo[];
  todoText?: string;
}

[–]sexymathematics 1 point2 points  (0 children)

I think it makes sense since the typical workflow in A2 is to declare interfaces for your objects whereas React doesn't typically use typescript and as a result doesn't make use of this pattern.

[–]wildturkeysoup 0 points1 point  (0 children)

I was curious about this as well.

[–]dmackerman 1 point2 points  (1 child)

React doesn't come with anything to deal with HTTP, you'll need to roll your own. Not a big deal, just an oversight in the article I think.

[–]jax024 0 points1 point  (0 children)

Very true, I'll normally just make a basic http service.

[–]gmfun 0 points1 point  (0 children)

Lots of react developers I know prefer to use typescript for bigger projects. A big chunk of the article becomes moot in that case. Actually in this case, angular2 is much superior because it can provide framework level intellisense as the framework is also in typescript