Our team has experience in Angular 1.0 and eventually moved to ReactJS + Redux. The main reason was due to there's no backwards compatibility if we were to migrate to Angular 2.0. Also, with ReactJS + Redux it is easier to model a single state application without any impact on performance.
---------------------------------------------
Senior Software Engineer
Globalisation Tools Engineering
DID: +61 3514 8262
Mobile: +614 2335 3457
Red Hat, Asia-Pacific Pty Ltd
Level 1, 193 North Quay
Brisbane 4000
Office: +61 7 3514 8100
Fax: +61 7 3514 8199
Website: www.redhat.com
Globalisation Tools Engineering
DID: +61 3514 8262
Mobile: +614 2335 3457
Red Hat, Asia-Pacific Pty Ltd
Level 1, 193 North Quay
Brisbane 4000
Office: +61 7 3514 8100
Fax: +61 7 3514 8199
Website: www.redhat.com
On Fri, Jun 10, 2016 at 6:46 AM, Ele Munjeli Mooney <elemunjeli@xxxxxxxxx> wrote:
Really nice rundown, Eric, thanks for that.
I've worked closely with some really great frontend dev teams in the last couple of years and I vote for React. The reason for this is that it seems for be preferred for efficient one way databinding which is a lot of the context for infrastructure applications (monitoring, viewing information, etc.) though it can still do the interactivity we'd need. Angular2 is causing my current team quite a lot of grief, though they are solid pros, and like Angular in general. I think it's probably overblown for what we want in this context.
We really should standardize an appy kind of stack. There's another thread talking about setting up dev boxes for infrastructure with docker or vagrant, and the ideal onramp I think would be to just pull down a scaffold (or generate one) into such a box for the premium infrastructure development experience. :)
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
