Putting aside all of the technical fun, from a pure reader perspective of <i>any</i> website sometimes I miss just simple boring HTML with a bit of CSS to make it more pleasant and readable. I don't know about anyone else, but particularly from a consumption standpoint I miss the days of 100k webpages.<p>I'm always stunned, but at the same time never surprised, when you discover a single webpage is 35+ MB, consuming 2GB of RAM, and consuming CPU as if it were a midrange video game.
I've looked at GraphQL a number of times. Does anyone have any practical examples of integrating it with backend(s), APIs, and/or specific databases?<p>So instead of "we use GraphQL, much love" + basic example and how it looks on React - a "here's how we take that structure and resolve it and return it." Because that structure looks amazingly sweet - but if in the background it's requiring circles of work, work and rework...<p>Anyhow, maybe I just don't understand it enough.
Do you guys think it makes sense for a newspaper to use React for the frontend?<p>I would think React might make sense for realtime dashboards and similar webapps.<p>But does it make sense for displaying articles, navigation and ads?
I tried Relay but found it ridiculously stupid that I need to change the graphql API on my server in order to satisfy the relay concepts(universal id, connections) so we rejected the idea and decided to go with the good old fashioned redux
That's cool to have here a synthetic explanation on how Relay can be more familiar.<p>I think I would just still be more attracted by Appollo framework which is more a redux-like syntax, so more consistent with all the workflow of the apps I used to develop. But maybe Relay has better benchmarks?<p>Also, if I want to stay REST but with optimist transactions between the backend and frontend, I prefer lighter lib like
<a href="https://github.com/tonyhb/tectonic" rel="nofollow">https://github.com/tonyhb/tectonic</a>
or even I just write some fast redux-saga watchers that helps to make my frontend always synchronized when my app calls a mutating db request.
This is very similar to the stack we use at BDG Media (bustle.com, romper.com, etc) We use Amazon Lambda, GraphQL, a custom model layer with data loader and redis, and preact. We haven't seen a clear benefit from Relay or Apollo with out front end apps (tbd on our admin apps) but we have enjoyed the Relay spec to help set server side conventions.<p>GraphQL has helped us make an api that is easy to understand, easy to change and and easy to use. We love it.
A website that should heavily depend on caching relies on tech that allows only POST requests (non-cacheable, non-idempotent) and hopes for workarounds later
Is anyone else here writing their GraphQL queries / REST calls in their components?<p>IMO coupling the data layer with the presentation layer is a terrible idea.