Add Aurelia to "Comparison with Other Frameworks"

[atsu85]

It would be nice, if the comparison also contained smth about Aurelia - I really enjoy using it myself.

[chrisvfritz]

A pull request and collaboration would definitely be welcome. My experience with Aurelia is quite limited, but I'd be especially curious to hear where Aurelia shines over Vue (even if it's subjective).

[atsu85]

I have (almost) no experience with Vue and I'm still reading the docs to find out more, but probably @EisenbergEffect and @jdanyow can introduce some strengths of Aurelia to figure it out.

[atsu85]

@chrisvfritz, here is link to the "Vue vs Aurelia" (that came out on top of the search results for me). It is a bit outdated for both frameworks, but probably outlines some good points (even if the first PRO of Aurelia made me laugh a bit regarding the gulpfile ;) )

[chrisvfritz]

Thanks. With that alone, I don't yet feel confident that I can make a good comparison between modern Aurelia and modern Vue, but I'd love for people to list differences they've experienced here.

[atsu85]

I asked from Aurelia chat about Aurelia vs Vue. I didn't get many replies, but one thing that couple of people outlined, was

• the lack of ES6/ES7 support.
• seemed to get complicated the moment you wanted to bring in 3rd party libs

From my own side, I'd add couple of things for Aurelia that came to my mind right now:

• Related to "ES6/7 support", for me TypeScript is very important because of compile-time checks and IDE support (refactoring and autocomplete).
• Aurelia has linter for detecting issues at compile time from templates (in addition to generic html syntax checks, aurelia specific html elements checks, binding syntax checks, static type checking and many more).
• Convention over configuration, but convention defaults can be altered case-by-case with decorators or replace default conventions with Your own. Aurelia custom element code looks a lot like Angular2 without the bloat.
• Easy to learn or even understand the code without knowing anything about Aurelia. You rarely need to open the documentation to look smth up even if IDE wouldn't help You in any way. This applies for both ES/TS and template code. My teammate once said (shortly after first contact with Aurelia), that he is surprised that things work just exactly how he thought they should without even reading the documentation).

For Vue I'd add

• server side rendering (corresponding feature for Aurelia is "nearly ready" based on the quote from main contributor)

[EisenbergEffect]

@atsu85 Do you use VS Code? We've got a cool plugin coming for that :)

[atsu85]

@EisenbergEffect,

Do you use VS Code?

No, I'm using IDEA, and while I'm grateful to @denofevil for an unofficial Aurelia plugin for IDEA, it could use much more love (from JetBrains).

[atsu85]

@EisenbergEffect, could You add some comments here regarding strengths of Aurelia?

[EisenbergEffect]

I'll start working on an official document.

[chrisvfritz]

@EisenbergEffect Excellent! If there's anything I can answer from the Vue end, please don't hesitate to let me know.

[MachinisteWeb]

I thinking the same thing when I traduce in FR this comparison.

Just from my experience :

• Aurelia is really a hugh library difficult to understand and apply without knowledge in MVVM.
• Vue is really simple to understand and the learning curve is really awesome !

So I prefer Vue.js because a lot of difficult things with Aurelia seems simple with Vue.

I don't know for a big application usage but for a everyday or simple / modest application usage, Vue is better than Aurelia for me.

But Aurelia have a nice name ;)