On Wednesday 08 October 2014 08:30:14 Bernard Poulin wrote: > I have not used ReactJS but from what I can understand, it is kept > lean and tries to include new concepts only when strictly necessary. > ReactJS seems to win on that front. > > On top of that, they focus a lot on "component"-ization. As of today, > it makes ReactJS *look *like the best option for projects that can > scale.
With ReactJS, especially for large applications, wouldn't you have to re-invent all those concepts for yourself when they are already there in AngularJS? Part of the job of an application framework such as AngularJS is to provide structure. It's fine if you don't want or need that. In that case you're better of with a library. However, in a large application you do need structure. It's great if you can some of that from a framework and its associated conventions. Not least, because you get a similar structure -- and similar problems + solutions! -- as other users of the same framework. If you come up with the necessary structure on your own and only as you go, chances are that it is not as robust as what an established framework could provide. Also, all problems with your own structure are your own problems as well and there's no community expertise to fall back on. Michael -- Michael Schuerig mailto:[email protected] http://www.schuerig.de/michael/ -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
