Angular is old (in the sense that it hasn’t kept up with the way JavaScript has evolved over the years) and lacks the foresight that its competitors have, most of which had the opportunity to take advantage of learning from Angular’s mistakes.
This topic surely has been beaten to death and back, but recently I’ve noticed a strange phenomena: people are arguing against languages introducing optional types and banishing the default-null concept by suggesting that these languages ignore the fundamental fact that you sometimes need a “nothing.”
Like many, I tend to try to shy away from tasks that aren’t directly related to writing code. Recently, I wrote my first installer for an application, and it made me think: “Why have I been avoiding doing this from the get-go for every project?”