mercredi 31 août 2016

Aurelia version upgrade policy

One thing I'd like to know about Aurelia is if it follows a compatibility-oriented update model similar to the Ember's one; I'm citing from a recent interesting article about Ember:

All the changes made in the 1.x releases are supposed to be backwards compatible, so in theory, you can upgrade from 1.3 all the way up to 1.11 with relatively few issues.

The way they do this is to incrementally deprecate things in the framework that they plan to remove, but they will keep the features (and tests) around for the entire 1.x series or otherwise shim them with compatibility layers. So while you are encouraged to resolve these deprecations as soon as possible, you are given a very long timeframe to do so.

I didn't found anything on the subject, but I discovered that Rob Eisenberg favours Ember above React or Angular, because it shares some of his design principles.

Does anybody knows anything about this?




Aucun commentaire:

Enregistrer un commentaire