The author recommends grabbing jQuery where necessary and I'd have to disagree. Instead they could look into ngOnChanges in the component lifecycle or using a d

The author recommends grabbing jQuery where necessary and I'd have to disagree. Instead they could look into ngOnChanges in the component lifecycle or using a different ChangeDetectionStrategy on the component. But maybe jquery is the better option for their use case. We're using it for an internal app at walmartlabs and its been great coming from angular 1. Working with angular-cli today is very stable and fully featured. I published a quick test module yesterday using angular-cli https://scttcper.github.io/ng2-adsense/ https://scttcper.github.io/ng2-adsense/ after gzip its small even with all of bootstrap v4's css included. It sounds like with ahead of time compilation we could see even faster first paint times combined with lazy loading of routes and modules it should be very fast even without using angular universal. Typescript is good, but I don't like tslint. I'm excited to see if eslint support for typescript goes anywhere: https://github.com/eslint/typescript-eslint-parser https://github.com/eslint/typescript-eslint-parser