|
As someone who has been doing web dev for a long time, I find it interesting that I can understand the author's points, but that I don't relate to them at all. For example, I agree that the angularjs to 'angular' transition was a bit wonky, but I don't understand having resentment or anger build up because I have to be a little more careful about how I craft search queries. It feels like he's frustrated with a lot of things, and once you get in that mindset, each irritant takes on huge significance. You don't start doing web dev because you really want to work with Angular, and I think that's the problem. You choose Angular because you think it will help you achieve an end-goal. I suspect that he started working on a codebase that had already chosen Angular and he had no buy-in. In that case, problems become frustrations, rather than just 'things to learn'. For example, the documentation on the module system is pretty good. It covers the reasoning, shows a basic example, and then delves in for when you need more information: https://angular.io/guide/ngmodules. Anyway, I enjoy working with Angular, but if something else works better for him, more power to him. |