Meteor Meets GraphQL
Arunoda Susiripala
14511

I’m very grateful for all the work you’ve put in to support the Meteor developer community, Arunoda Susiripala!

I was wondering, though, whether you plan to eventually make this project front-end agnostic at some point (instead of leading users to only walk down the React JS path). You mentioned that you could support Angular (V1?) as well as React; would users be able to drop in other front-end frameworks like Aurelia as well?

(If you’re not familiar with Aurelia, see https://atmospherejs.com/tsumina/meteor-aurelia for one method of integrating Aurelia with Meteor, or visit the Aurelia home page here: http://aurelia.io/)

For those of us who are not necessarily interested in diving into a Domain Specific Language variant of Javascript (like Facebook has constructed with their JSX syntax), an option like Aurelia that leverages the new features of Javascript coming from ES2015/ES6 (as well as some ES7 features), Aurelia looks like a pretty good alternative to React – especially when you compare the performance of Aurelia and React…

Spoiler: Aurelia outperforms React.

  • See http://blog.durandal.io/2015/12/04/aurelia-repaint-performance-rules/
  • And for the implementation of the performance test, see here: http://jdanyow.github.io/aurelia-dbmonster/
  • Or for a comparison of React and (an earlier version of) Aurelia, see http://ilikekillnerds.com/2015/03/aurelia-vs-react-js-based-on-actual-use/

To sum up, I was just wondering if you had any thoughts on using your new solution “Mantra”, Meteor, and GraphQL with alternative view layers to React, such as Aurelia?

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.