- attracting talent
- hard to debug
- no good developer tools
- template is very hard to debug
- framework is very verbose, lots of coupling
- harder to separate concerns
- growth of knowledge via conferences and talks - risk of stagnant
- future support
- code maintainability + extension
- bundle splitting / tree shaking
- state management in angular
- peeling the curtain behind the magic
- maintaining multiple versions vs. faster to build new things
- user experience degradation
- developer happiness
- React
- VueJS
- Angular 5
- Velocity
- Productivity
- Context Switching
- Training
- Developer Happiness
- Devops Impact
- Devtools
- Build Tools
- Compilers
- Testing
- Good documentation
- Third party libraries
- Community / Support
- Error reporting
- Server Side Rendering Capabilities
- Production ready
- Roadmap of Changes
- Emergent vs. Established
- Learning Resources and Experts
- Native code support
- Adoptions
- Other “success stories” of adoption and support
- What is Hubba’s “perfect” frontend
-
What is an acceptable migration goal?
- nightmare scenario - no one wants to work on this application
- how do we get our stuff over to the users where it feels unified
- Testing concerns
-
How do we get competency on the new framework?
- coverage on the team
- coverage on tests