Dangers of up keeping up with the Angular release schedule?
10 views
Skip to first unread message
Kyle S
unread,
Jul 15, 2020, 9:29:13 AM7/15/20
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Angular and AngularJS discussion
Hello all,
My company is exploring Angular2+ as a technology for a large, complex application.
Our development cycle is much longer than Angular's release cycle, and we don't expect to be able to manage doing upgrades every 6 (or even every 18) months.
What sort of issues would we likely encounter by choosing to stay on an old version and not upgrading?
Will updated browsers eventually stop being able to support our application? Any other complications come to mind?
Would AngularJS be a better choice in this scenario?