<story><title>Reactive GraphQL</title><url>http://info.meteor.com/blog/reactive-graphql</url></story><parent_chain><item><author>bwhitty</author><text>Meteor is about the UX.&lt;p&gt;The ease of getting up and running, the ease of tools, and the ease of deployment. On no React stack can you (and in the future this will be more simple) run&lt;p&gt;&lt;pre&gt;&lt;code&gt;  meteor create my-react-project
  npm init &amp;amp;&amp;amp; npm install react
&lt;/code&gt;&lt;/pre&gt;
And start coding JSX, ES2015&amp;#x2F;2016 immediately. There is a non-trivial amount of boilerplate and configuration you need to do to get this working my hand, and while it can provide a greater level of control, it undoubtedly adds to the overall weight of code you need to maintain.&lt;p&gt;Then hypothetically after some time of development, do&lt;p&gt;&lt;pre&gt;&lt;code&gt;  meteor add-platform ios
  meteor add-platform android
  meteor add-platform desktop (this is theoretical currently, but there exist packages which do exactly this)
&lt;/code&gt;&lt;/pre&gt;
And have Cordova iOS and Android builds, and an Electron desktop app. Then in a few weeks, do&lt;p&gt;&lt;pre&gt;&lt;code&gt;  meteor deploy
&lt;/code&gt;&lt;/pre&gt;
and have a fully monitored application up and running on AWS with Meteor&amp;#x27;s monitoring and deployment tools. Meteor&amp;#x27;s play is in the ease of these tools. It is absolutely non-trivial the amount of glue and knowledge you need to create, understand, and maintain the current (and ever-rapidly expanding) Javascript toolchain.&lt;p&gt;This announcement touches on one of their most thorny issues of being tightly coupled to Mongo. Adding this abstraction layer allowing any UI and any data source is Meteor&amp;#x27;s ticket to the masses.</text></item></parent_chain><comment><author>faceyspacey</author><text>When thinking about Meteor&amp;#x27;s value proposition, it&amp;#x27;s been neck and neck between what you&amp;#x27;re saying (which is that of a &amp;quot;universal build tool&amp;quot;) vs. it&amp;#x27;s full stack reactive subscription capabilities. Both of which have been Meteor&amp;#x27;s 2 most important features.&lt;p&gt;That said, on the build side of things Webpack and Babel have been giving Meteor a run for its money. It takes more work to build your app with those tools, but it&amp;#x27;s a lot less work than it used to be using plain NPM, and you now have a lot more customization than in Meteor.&lt;p&gt;That&amp;#x27;s why doubling down and continuing the thought of full stack reactivity is so important to Meteor. I&amp;#x27;m so glad to hear that they have suited up to upgrade their reactive server-side parts. I hope they put a lot of resources behind it.&lt;p&gt;If interested, here&amp;#x27;s my take my take on what &amp;quot;Reactive GraphQL&amp;quot; means to Meteor developers:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;@faceyspacey&amp;#x2F;what-reactive-graphql-means-for-meteor-3be285bce0b6&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;medium.com&amp;#x2F;@faceyspacey&amp;#x2F;what-reactive-graphql-means-...&lt;/a&gt;</text></comment>
<story><title>Reactive GraphQL</title><url>http://info.meteor.com/blog/reactive-graphql</url></story><parent_chain><item><author>bwhitty</author><text>Meteor is about the UX.&lt;p&gt;The ease of getting up and running, the ease of tools, and the ease of deployment. On no React stack can you (and in the future this will be more simple) run&lt;p&gt;&lt;pre&gt;&lt;code&gt;  meteor create my-react-project
  npm init &amp;amp;&amp;amp; npm install react
&lt;/code&gt;&lt;/pre&gt;
And start coding JSX, ES2015&amp;#x2F;2016 immediately. There is a non-trivial amount of boilerplate and configuration you need to do to get this working my hand, and while it can provide a greater level of control, it undoubtedly adds to the overall weight of code you need to maintain.&lt;p&gt;Then hypothetically after some time of development, do&lt;p&gt;&lt;pre&gt;&lt;code&gt;  meteor add-platform ios
  meteor add-platform android
  meteor add-platform desktop (this is theoretical currently, but there exist packages which do exactly this)
&lt;/code&gt;&lt;/pre&gt;
And have Cordova iOS and Android builds, and an Electron desktop app. Then in a few weeks, do&lt;p&gt;&lt;pre&gt;&lt;code&gt;  meteor deploy
&lt;/code&gt;&lt;/pre&gt;
and have a fully monitored application up and running on AWS with Meteor&amp;#x27;s monitoring and deployment tools. Meteor&amp;#x27;s play is in the ease of these tools. It is absolutely non-trivial the amount of glue and knowledge you need to create, understand, and maintain the current (and ever-rapidly expanding) Javascript toolchain.&lt;p&gt;This announcement touches on one of their most thorny issues of being tightly coupled to Mongo. Adding this abstraction layer allowing any UI and any data source is Meteor&amp;#x27;s ticket to the masses.</text></item></parent_chain><comment><author>enobrev</author><text>I think I get your point, and while I haven&amp;#x27;t done much with meteor since a few weeks after it was first announce, I recently started a couple react.js projects using jspm.  I&amp;#x27;m not sure, yet, if jspm is ready for prime-time, but getting started was as simple as:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    npm install [-g] jspm 
    jspm init
    jspm install react
&lt;/code&gt;&lt;/pre&gt;
For es6&amp;#x2F;es7, adjust config.js babelOptions.&lt;p&gt;I&amp;#x27;ve nothing to add in regards to ios &amp;#x2F; android &amp;#x2F; desktop, but for getting up-and-running, jspm seems to do the job quite well.</text></comment>