Have Angular engineers invaded this thread? There's a lot of condescension and downvoting being thrown around for anyone who dares question the update cycle.
The concerns of rapid major updates are legitimate. Angular is a framework, not an application. With a complex app, you can't just reboot your code and have it work. People invest lots of time and money building and testing a project, and refactoring because of a major release costs both time and money.
Stability is a major factor when it comes to adoption (for the above reason), and that has cascading effects. Large companies -job providers- tend not to pick frameworks which require significant overhauls just to keep it functioning and secure. And the larger the company, the more important that stability becomes.
To be fair, this isn't just a problem with Angular, it's prevalent in many front-end tools. While every developer understands -and even promotes- the concept of constantly improving tools, there's a threshold, a balance, when it comes to releases. If you are constantly changing your ideas, perhaps your ideas need to sit in the oven a little longer before they're released.
1
u/TheBigLewinski Oct 19 '18
Have Angular engineers invaded this thread? There's a lot of condescension and downvoting being thrown around for anyone who dares question the update cycle.
The concerns of rapid major updates are legitimate. Angular is a framework, not an application. With a complex app, you can't just reboot your code and have it work. People invest lots of time and money building and testing a project, and refactoring because of a major release costs both time and money.
Stability is a major factor when it comes to adoption (for the above reason), and that has cascading effects. Large companies -job providers- tend not to pick frameworks which require significant overhauls just to keep it functioning and secure. And the larger the company, the more important that stability becomes.
To be fair, this isn't just a problem with Angular, it's prevalent in many front-end tools. While every developer understands -and even promotes- the concept of constantly improving tools, there's a threshold, a balance, when it comes to releases. If you are constantly changing your ideas, perhaps your ideas need to sit in the oven a little longer before they're released.