I did a project in ng2 using babel and some of the flow transforms, which worked okay, you definitely need something to handle the decorator syntax as without it, it's *really* not nice to build ng2. I don't think it was bad, though I did go through growing pains with the router, and even then, it changed again since I had handed off that app around 8 months ago. Wiring up redux with the router was particularly painful (twice) but syncing the two is really important if you're going to use a redux store at the core of your app state.
From my relatively light exposure, it's really worth digging into Redux for state management, it will make the logic in growing an app much more consistent. It's not easier than flying by the seat of your pants, but the pain you pay upfront is more than made up for as an app grows. Beyond this, that workflow can be used with different rendering options from ng2 to react and others... The ecosystem isn't finished growing and a trend towards web components will probably continue. Working with unidirectional state management workflows, however is unlikely to go away as it just makes more sense in medium to large complexity apps. And works well enough in lower to medium complexity.
(my comment, copied from tfa's comments secion)
tracker1 2775 days ago. link 2 points ▲ ▼