1. The build ecosystem. We started with JSPM which has a lot of annoying issues, worst of all a +-700Mo base install that takes 45min to complete, which makes docker deploys really slow. Another annoyance is a config.json that is re-generated each time you make a gulp watch and pollutes git diffs. The export config must be manually modified each time we add a new library or assets and is also a source of errors. We tried replacing it with aurelia-cli but couldn't get it to work with some external dependencies. We are considering moving to webpack.
2. Probably related to jspm but loading our applications takes 3-10secs depending on the platform and thus requires a loading screen, which I find unacceptable.
2. The documentation is in a web-application and is not indexed by Google.
3. Some modules have a javadoc style documentation that requires a lot of reading to do simple stuff.
4. The templating engine is missing an 'else' keyword.
5. Watching for model changes requires manually setting up a watcher and manually tearing it down, Vue's watchers are far easier to setup.
6. Aurelia is split into many small libraries which means you have to manage a lot of import directives.
7. Aurelia-validation was depreciated and replaced by an incompatible library without much warning, and without migration instructions.
8. Aurelia implements model watching by replacing all fields with getters and setters and thus pollutes the models when inspecting them with chrome developper tools.
9. Aurelia implementation outputs a lot of warnings when using Bluebird.js with default settings.
Otherwise as I said the underlying architecture is fine, but those annoyances add-up. It just needs more polish.