Thanks to hard-working core team of Au2, still going well with it. I just don’t see a need for the other frameworks and you end up with similar problems in those other frameworks.
There is still a big chance of Au2 having the strike potential to take down the other frameworks down a peg because there is still so much in terms of inefficiency of a lot of SPA frameworks and the way they are coded.
I’ve always had just such an easier time working with and teaching Au1 and even Au2.
Aurelia is alive and well. AcumaticaERP, the worlds fastest growing cloud ERP just released the preview version of their new Modern UI based on Aurelia.
By virtue of this there will be hundreds of current developers moving from ASPX WebForms to Aurelia-our developer being one of them.
Nice!
May I ask what you did with all the outdated dependecies though..? We also still use AU1, but since 1 is outdated and 2 does not even have a final version nor “traction” by the community, we are not sure what to do.
I’m not in the code on a daily basis so I don’t know which dependencies are outdated and how they’re handling that. My guess is that Acumatica is just using those outdated dependencies as-is(stability is the main priority). You can download the source code for the latest Preview here(requires Windows): builds.acumatica.com - /builds/
I know four Australian companies using Aurelia in production. Two are already on Aurelia 2. One is migrating a massive 7yo Aurelia 1 app. Another left their v1 app as-is and started a new greenfield project on v2. These teams looked at the other options and still chose to stick with Aurelia. That should tell you something. I also know of a couple of companies over in Europe using it for large-scale projects too (one of them is using it for a mobile application).
Aurelia 2 isn’t dead. We’re nearing a stable release. The big architectural changes are done. The framework is fast, stable, and unopinionated in all the right ways. No runtime magic, no forced patterns, no churn.
In-fact, I would highly recommend migrating to Aurelia 2 now or using it for greenfield projects. Truthfully, Aurelia 2 has been in a usable state for migration and new projects for a long time now. We have avoided the stable tag primarily due to some big core changes (like the async binding refactor work, making router-lite the default router package, etc).
Docs are in great shape. I’ve got another big batch of updates going out soon. Core features are implemented. Bugs have been closed. GitHub activity is constant. We’re not rewriting the framework every 12 months. We’re tightening the bolts.
For anyone having doubts - do not hesitate to use Aurelia 2
Over a year ago decided to use Aurelia 2 in our project, despite having doubts due to obvious reasons. The framework proven to be super stable, the development experience is very smooth and the docs are comprehensive.
There were some major breaking changes in the framework along the way:
TypeScript autoinjection gone due to changes in decorators - however this approach to DI was never explicitly stated to be correct, so might be as well my fault we used it in the first place.
Dialog API
Swapped default “router”
We were affected by all three changes, even took the hard way when it comes to router (instead of just swapping imports, decided to take the occasion and migrate the app to router(-lite))
Frankly speaking, neither of the migrations was too difficult to deal with.
I also occasionally work with a legacy project that still runs Aurelia 1 to this day. I’m impressed with the fact that the list of differences in the surface API and the development workflow between Au1 and Au2 is reasonably short, making it much easier to contribute simultaneously to both Au1- and Au2-based projects. Usually switching between projects based on different generations of frameworks takes much more effort to get used to updated APIs etc.
On a related note, the new docs now have a passionately worded philosophy section inspired by the Ruby on Rails doctrine which outlines what Aurelia is all about, what drives the framework and what it stands for: The Aurelia Philosophy | The Aurelia 2 Docs - it’s designed to be impactful in some parts, provoking in others and serves as a good outline of why you should choose Aurelia over something else.
