[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.