[majora2007]

What's interesting to me is that it seems a lot of people got burned by AngularJs (Angular 1) and now swear off Angular as a whole.

Like many, I came from pre-SPA days -> AngularJs -> Angular 2 -> Modern Angular. I tried react a few times, plus React Native but found it hard. I wasn't good with a slightly different render-syntax (whereas Angular uses HTML) and every project I was on was wildly different from each other.

Modern Angular has been wonderful. A lot of the pain points people have are gone, some good parts of other frameworks (signals, single-components vs modules, etc) have been incorporated and embraced.

[WorldMaker]

For what it is worth, I missed AngularJS/Angular 1 and managed to use Aurelia to avoid several versions of Angular 2+. When I did get eventually pressured into working on Angular it was a nightmare for several reasons. One of them was I got hugely burnt by Zone.js. Angular is finally doing something about Zone.js years after my warning. (Though it took Signals to push them to do it, which is another rant because Signals are just dumber Observables and Angular already has an RxJS dependency.)

> (whereas Angular uses HTML)

Angular has as complex a template language as any other major framework. The fact that it uses .html files is a convenient lie to make it seem like it is "just HTML". Its template compiler is a far more complex beast than JSX. (And it doesn't have anything like half the type safety of TSX.)

[em-bee]

happy to see another fan of aurelia here.

i actually started with angular 1 before it became popular. i evaluated the alternatives at the time, knockout, ember and a few others, and angularjs just looked the best. finally when angular 1 was no longer maintained i discovered aurelia, in part because rob eisenberg had an interesting story about how he got invited to the angular team because of his ideas, and how he left again because he could not actually get his ideas implemented.

it's a bit disappointing that development of aurelia 2 is slow going, but in some ways i consider that a good thing, considering how fast vue and svelte are evolving away from what they were originally.

i need to look at solid.js though. the only promising newcomer in resent years if the state of js survey is any indication.

[WorldMaker]

I was more of a fan of Durandal, which was Aurelia's predecessor. It was a SPA wrapper around out-of-the-box Knockout. It seemed cleanly focused and was useful in that you didn't need to learn a different view engine if you were already using Knockout.

Following Rob's blog because of Durandal was a part of how I landed on "try to avoid Angular" and it did give me Aurelia as a bit of arsenal to say "hey, this framework is enough like Angular that it should feel comfortable to work in" for a time.

I never did end up liking Aurelia more than Durandal, but I certainly liked it more than Angular.

[em-bee]

makes sense. i was obviously coming from angular, and as i said before, i did look at knockout and i found angular was the better choice. so i guess aurelia's appeal then came naturally. but then i didn't know about durandal, so i can't say how much i would have liked it. but this tells me that angular had a stronger influence on aurelia than i was aware of. that's not surprising of course, but still interesting.

[BartBM]

As a React developer, I think Aurelia 2 is the best JS/TS framework today. I always use Aurelia for personal projects.