Vuejs.org: 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.

[Haeresis]

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 ;)

[ferrygr]

Comparing cross platform support and portability between Vue and Aurelia is very welcome. How easy can each be ported to iOS or Android? How mature is the tooling for this? For instance, from what I've gathered, React is very portable - web and mobile devices run the the same code more or less.

Some more information about the development efforts behind Aurelia and Vue. It seems that Vue is a one-man effort, and depending a project on a framework having a bus factor of one is not acceptable imo. How is the situation for Aurelia?

[chrisvfritz]

@ferrygr Just FYI, Vue's definitely not a one-man effort these days. 🙂 The core team includes 21 members as of writing. Many of the official repos are mostly maintained by people other than Evan and even in core, commits now tend to range between 20% to 60% from other people.

If Evan got hit by a bus, it'd definitely be a very sad day and an incredible loss for the community. Vue wouldn't be the same without his vision, but it would go on.

[20zinnm]

I would definitely add "Official Jetbrains plugin" as a plus for Vue, as well as community. However, I do like the naming conventions Aurelia adopts--value.bind--but I still think Vue is an overall cleaner framework or library.

[marccollin]

@chrisvfritz

when you check contributor, second after evan have less then 4000 line of code...

[sdras]

As Chris and I have limited experience with Aurelia and no PR was submitted despite the issue being most active about a year ago, I'm going to close out this issue. Please feel free to reopen it! Especially if someone would like to take the charge of creating the initial PR that we could work off of. We appreciate your time thus far in this consideration.