TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Reactive GraphQL

158 点作者 johanbrook超过 9 年前

7 条评论

bwhitty超过 9 年前
Meteor is about the UX.<p>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<p><pre><code> meteor create my-react-project npm init &amp;&amp; npm install react </code></pre> And start coding JSX, ES2015&#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.<p>Then hypothetically after some time of development, do<p><pre><code> meteor add-platform ios meteor add-platform android meteor add-platform desktop (this is theoretical currently, but there exist packages which do exactly this) </code></pre> And have Cordova iOS and Android builds, and an Electron desktop app. Then in a few weeks, do<p><pre><code> meteor deploy </code></pre> and have a fully monitored application up and running on AWS with Meteor&#x27;s monitoring and deployment tools. Meteor&#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.<p>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&#x27;s ticket to the masses.
评论 #10971646 未加载
评论 #10971611 未加载
评论 #10971663 未加载
评论 #10971510 未加载
评论 #10971744 未加载
davnicwil超过 9 年前
Each successive post of the recent set from meteor just seems to be bringing it further towards resembling the features of a GraphQL &gt; Relay &gt; React stack - in fact actually using React, and now it seems, GraphQL.<p>This is great because the promise of a stack like this is <i>very</i> exciting, but I am left wondering what is meteor promising to bring that isn&#x27;t just bundling some modules, and re-implementing Relay?<p>I can&#x27;t see anything in the list of <i>what we are planning to build</i> that isn&#x27;t already offered by Relay, or on Relay&#x27;s roadmap.<p>Not that a different implementation isn&#x27;t a great thing, competition is always advantageous, but my understanding is that Meteor is a for-profit company whose product <i>is</i> their framework - it seems quite odd therefore that their plan for that framework appears to be to just piece together and&#x2F;or re-implement an already-existing, well-used and well-known stack of completely open-source libraries, that aren&#x27;t at all difficult to piece together as it is. What&#x27;s their strategy here?
评论 #10970882 未加载
评论 #10971453 未加载
评论 #10971060 未加载
Matthias247超过 9 年前
Is Reactive GraphQL even specified? I thought that in the current state GraphQL only defines single queries (snapshots) of data, and not continuos update notifications. Forgive me if I have missed it - I have not followed GraphQL&#x2F;Relay apart from a very basic look at it.<p>Without having an open specification Meteors implementation might end up completly different or incompatible to other (Reactive) GraphQL implementations.<p>Despite that, I think that implementing a reactive GraphQL backend will be very hard, and it would only work good if all of the sub-data-sources that you use in your backend support reactivity (subscriptions) as well. If they do, then you have to subscribe to all possible data sources that are mentioned in the query, and update the current state when one of these changes. If the update requires you to fetch an additional data source (e.g. you must fetch other indexes of data which are provided by another source), you must even dynamically subscribe&#x2F;unsubscribe on updates of other sources.<p>And how can you provide traditional REST APIs (or even query-based GraphQL endpoints) as reactive endpoints? The best you can do is probably implement polling (rerunning) the query on the backend over and over.
评论 #10973175 未加载
daxfohl超过 9 年前
I&#x27;d recommend rebranding and a big-bang launch. Enough people were put off by meteor that incremental improvements don&#x27;t excite. Kind of the opposite of the boiling frog thing.
d0m超过 9 年前
What about offline support? This is one of the most tricky part.
评论 #10971707 未加载
rottyguy超过 9 年前
Is anyone playing with GraphQL outside of js? Am interested in using it for a project at work and wondering what&#x27;s it like in something lower like c&#x2F;c++.
评论 #10972882 未加载
评论 #10971690 未加载
评论 #10971324 未加载
jFriedensreich超过 9 年前
i would be interested why they decided against falcor style json graph instead of graphQL