Aurelia is a next generation framework that leverages modern concepts like ES6, Web Components, and modularization to help you develop performant, futureproof applications.
Aurelia is the natural progression of Durandal, an AngularJS competitor built by Rob Eisenberg. Aurelia’s history involves a number of encounters with the AngularJS team over the years. It’s for this reason that many aspects of the framework might feel familiar to the AngularJS developers among you.
As I said, Aurelia is a “next generation” framework and as a consequence the tools it uses may be new to some of you. It runs on Node.js, and uses npm but it relies on a few cool new pieces of tech that we’ll look at briefly below:
This one isn’t so new but it’s a core part of Aurelia’s setup. We’ll use Gulp to pipe all our files through various tasks to ensure our application is all wired up and ready to go.
The ES6 module loader is a pollyfill for the
System dynamic module loader that was part of the original ES6 specification. The
System loader is in the process of being written into browser specifications but in the meantime this polyfill provides a futureproof solution that we can use today.
Continue reading this article on SitePoint
Also, try not to view this as a stuck up programmer trying to correct you for doing something “wrong”. I’m just trying to spread the word about what I (and many others) have come to see as a best practice and prevent the spread of what we consider to be bad practice. I hope you’ll consider it.
@joezim007 - could you give some examples of too much logic in the templates?
As far as I am concerned, I need two types of logic. Data binding/replacement and HTML/DOM manipulation. Aurelia does both well and more pragmatic than Angular from what I can tell. But, I am far from an expert in such matters too. So I’d like to know what you think is to much logic. Thanks.
- I think that event handling should be taken out of the DOM (e.g.
- Loops and other control structures just don’t seem right when used as attributes of an element rather than on their own. (e.g.
<li repeat.for="el of collection">) This isn’t about too much logic, just strangely done logic.
It’s not nearly as bad as Angular and Ember who use templates to do a lot more, but I’m used to Backbone and Ampersand where you have more of the logic in the classes rather than in the template. Templates should be dumb so that they can be mostly written by non-JS devs.
Can this only be used in nodejs? Or can be ran on PHP Stack?
Aurelia is a frontend JS framework. It has nothing to do with the server side.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.