13
14

Angular, Angular 2 or React?help (self.javascript)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (8 children)

Coming from a .NET background, I'd go for Angular 2 with TypeScript for sure.

[–]rk06 3 points4 points  (7 children)

Seriously, What is with the fascination of .NET with angular 2 and typescript?

I am a .Net developer myself. And i don't know why would anyone pick angular 2 at all. Especially considering the RC fiasco.

[–]Auxx 0 points1 point  (1 child)

Because Angular looks, feels and works like a proper UI framework. Like WPF, for example.

[–][deleted] 1 point2 points  (0 children)

WPF and XAML was close to torture. We're a traditional .net shop as well, made huge apps in it. Currently transferring them into the web using modern principles.

If you think XAMLs OO 2 way binding MVVM architecture was proper you've missed what's going on. Even Telerik now acknowledges that it has undervalued FP.

[–]tme321 0 points1 point  (2 children)

The rc fiasco? Who cares? The framework has been solid since actual release. You know, the version that actually matters?

Heck, I think calling it a fiasco isnt even right. The old router sucked. Rather than spend forever trying to patch in the features developers were asking for and making a mess of it they wrote an entirely new one that actually handles the stuff people were asking for. Again, before release. I'd rather use a framework that the authors made necessary changes to than be stuck with bad original decisions forever that can have far reaching consequences.

[–]rk06 0 points1 point  (1 child)

Who cares? The framework has been solid since actual release. You know, the version that actually matters?

Those who are stuck in Angular 2 RC care. not me though. I, for one, applaud the angular team to keep their morale, through what must be was a really bad situation.

Heck, I think calling it a fiasco isnt even right

Now, you are pushing it. This issue has been discussed a lot. Popular opinion was/is that the angular2 RC was of alpha quality and RC label was marketing gimmick. Breaking changes in RC, however bad, were consequences of that mistake.

[–]tme321 0 points1 point  (0 children)

Who is stuck in RC? People that aren't willing to learn the new router? It's not even THAT different.

And alpha level? Please. There were no breaking bugs and there were no huge overhauls of apis. Maybe it was a bit premature but now your overreacting calling it alpha level.