2 ms·

Has anyone used Aurelia with succes? I'm currently looking into what our next client side framework should be and I have a really good feeling about Aurelia. I

Has anyone used Aurelia with succes? I'm currently looking into what our next client side framework should be and I have a really good feeling about Aurelia. It feels like someone finally got it right. It's the same feeling I had about ServiceStack, which is by far the best web framework I've ever used. My main criteria is ease of use by backend devs and going by the tutorials I've done so far, that certainly seems to be the case. I am however myself a backend guy and it's quite likely that Aurelia is missing something important or that the niceness breaks down once you cross some complexity threshold, and I can't see that due to my limited experience in that field.

chadporter 10y ago
We've been using Aurelia in production since early beta. Have a half dozen live projects in it now, including Cordova apps (but not Electron apps). It's been great. Very easy to work with and good performance these days. The best part IMO is that you don't really get sucked into an Aurelia-or-nothing situation. It's not hard to work with other techs right inside your Aurelia app. We often had a dev that was less familiar with the possibilities in Aurelia do stuff using technologies they already knew, and then we'd convert it to use Aurelia methods later after the feature was proven. Most of the gotchas I've run across are related to observing arrays. By default some array mutations aren't caught. There are ways around this by manually importing the BindingEngine and setting up a subscription, or using @observable on a property, but before you figure that out array observation is a bit vexing. It's not that these other methods are hard, it's that you have an expectation of collection observations and the way it works (largely for performance reasons) doesn't mesh with that. It does pay to have someone familiar with Aurelia and not all dabblers. We do a good bit of advanced stuff like dynamically generating bindings based on conditions defined in data (e.g. show/hide this form field if these other arbitrary form fields have these arbitrary values, which can be changed by the user, and automatically rebind to the new fields when conditions are changed). Doable if you use some of the more core Aurelia features, but not really something you can do with just the basic surface APIs. Aurelia or not, all of our architecture is front end + app-agnostic API. Backend devs don't need to give a crap about Aurelia if they don't want. If you mean "is it easy for backend devs to do front end work using this?", I don't know because we don't have any pure backend guys for me to use for reference.
toddwprice 10y ago
We are using Aurelia in production, and it is a joy to work in. It gets out of the way as much as possible but does so much for you without you having to do much. The biggest pain point is the build/deploy step takes some work to perfect, but this is being worked on by the community and is a pain for every front-end SPA framework. As far as ease of use by backend devs, I'm not sure what you mean as the back end can be anything you want. We use a Node.js API for our back end, but use whatever you want to create a REST service and Aurelia will consume it just fine.

chadporter 10y ago

We've been using Aurelia in production since early beta. Have a half dozen live projects in it now, including Cordova apps (but not Electron apps). It's been great. Very easy to work with and good performance these days. The best part IMO is that you don't really get sucked into an Aurelia-or-nothing situation. It's not hard to work with other techs right inside your Aurelia app. We often had a dev that was less familiar with the possibilities in Aurelia do stuff using technologies they already knew, and then we'd convert it to use Aurelia methods later after the feature was proven. Most of the gotchas I've run across are related to observing arrays. By default some array mutations aren't caught. There are ways around this by manually importing the BindingEngine and setting up a subscription, or using @observable on a property, but before you figure that out array observation is a bit vexing. It's not that these other methods are hard, it's that you have an expectation of collection observations and the way it works (largely for performance reasons) doesn't mesh with that. It does pay to have someone familiar with Aurelia and not all dabblers. We do a good bit of advanced stuff like dynamically generating bindings based on conditions defined in data (e.g. show/hide this form field if these other arbitrary form fields have these arbitrary values, which can be changed by the user, and automatically rebind to the new fields when conditions are changed). Doable if you use some of the more core Aurelia features, but not really something you can do with just the basic surface APIs. Aurelia or not, all of our architecture is front end + app-agnostic API. Backend devs don't need to give a crap about Aurelia if they don't want. If you mean "is it easy for backend devs to do front end work using this?", I don't know because we don't have any pure backend guys for me to use for reference.

toddwprice 10y ago

We are using Aurelia in production, and it is a joy to work in. It gets out of the way as much as possible but does so much for you without you having to do much. The biggest pain point is the build/deploy step takes some work to perfect, but this is being worked on by the community and is a pain for every front-end SPA framework. As far as ease of use by backend devs, I'm not sure what you mean as the back end can be anything you want. We use a Node.js API for our back end, but use whatever you want to create a REST service and Aurelia will consume it just fine.