I quite like Angular, it's a bit lite Django with batteries included.
Very organized, TypeScript(!), reusable components, easy to write tests, create models, call Rest end-points for data, routing, make lazy loaded modules, scss and so on. Documentation is superb.
It took me only a few days to learn and become productive.<p>I tried React but it felt very incomplete and to get things done beyond the basic tutorial I had to go all over blogs, articles and forums to find instructions (often incomplete or out-of-date).
Still it required a complicated process to get data from a SpringBoot server (I was told I need to add Redux, then some other http library for the actual calls. Then try to tie everything together... well, I gave up.)<p>That was a year ago and I'm sure it's better now, but Angular at that time was very mature compared to the hackish React.
Working with anything new can be a humbling, frustrating experience. In some sense, this <i>is</i> the job of programming. (Why would you write the same code over and over again?)<p>That said, I’d be interested in hearing what kind of “first-time encounter” experience the author is looking for, and whether he’s found it in another tool. Barring that, at least some more specifics on the troublesome areas, something like bug reports, e.g.<p>“I <i>expected</i> one thing, but I <i>actually got</i> another. Here’s why that’s bad.”
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.<p>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.<p>It feels like he's frustrated with a lot of things, and once you get in that mindset, each irritant takes on huge significance.<p>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.<p>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: <a href="https://angular.io/guide/ngmodules" rel="nofollow">https://angular.io/guide/ngmodules</a>.<p>Anyway, I enjoy working with Angular, but if something else works better for him, more power to him.
Anyone out there who has experience that maybe isn't so bad? I am just about to take a job where I'll be ramping up on Angular 7. I'll be coming from React which has its own problems and complaints, but it's more of a love-hate thing with React (and a good amount of the former). This article has absolutely nothing nice to say about Angular. What have I gotten myself into??
the author's rant doesn't make him sound very intelligent.
There isn't strength to any of his points, for anyone who has spent more than half-assed effort at trying to learn Angular.
I associate with this so much it hurts. I have wasted thousands of my employers dollars just waiting for this pile of shit to compile or run.<p>If you like light, fast, opinion free UI tools, maybe give my module fastn a go: <a href="https://GitHub.com/korynunn/fastn" rel="nofollow">https://GitHub.com/korynunn/fastn</a>
Not the point of the article, but how exactly did the iPhone's utility flatline because they removed the headphone jack and how is a headphone jack a "vital" feature, considering the rise in popularity of blueetooth headphones and the fact that the iPhone ships with the 3.5mm dongle?