If you have two fields in a query, does that mean two resolve functions? If I using a SQL database and the two fields were stored on two columns on the same table, wouldn't that cause 2 SQL queries to be run?
I'm a big fan of React but it took me a year after its introduction for me to get it and like it. What particularly did the trick for me was one of Pete Hunt's talks he gave a year after release acknowledging the confusion and explaining the reasoning for React rather than just the technology itself.
I feel like GraphQL can be something great and the pain points they identify with typical APIs are stuff I've felt but GraphQL just feels incomplete to me. I feel they're focusing too much on what GraphQL looks like on the client-side and not enough what it looks like on the server-side. The biggest question I have is what's going to process the GraphQL query on the server to fetch the data from the actual datastore? What does that look like when working with typical datastore such as a SQL-based database? The closest thing I've seen that answered that question was this blog post[0] which doesn't look very appealing if that's what the server-side implementation is going to look like. The blog post's implementation looks like a more complicated version of my own APIs which are usually a series of custom endpoints based on my client's needs. I don't see the big deal right now. Maybe next year...
The docs page delivered 270kb of compressed and minified JavaScript (1MB uncompressed) but sadly didn't seem to show anything with JavaScript disabled. I thought all the hot new React apps were isomorphic nowadays.
This reminds me of morning routine back in grade school called "Mad Minute" where we would be given a sheet containing 30 or 50 simple equations to solve. You'd have to complete it in a minute and the teacher would stopped grading at the first wrong answer so getting the first one wrong follwed by 49 correct answer would net you a score of zero.
When I first transferred to that school I was terrible at it but I did get pretty good at it later on. I think it did a lot for my arithmetic skills.
There was a guy who joined the Knockout or Angular team (I forget which) since they had similar ideas for the future of their frameworks. Not too long later, he left them and restarted his project as their vision began to diverge.
I don't know why anyone would want One True JS framework. Many of them provide different things. Angular has the kitchen-sink approach handling everything from templating, model-binding, routing and ajax requests and on the other end of the spectrum there are small libraries that do one thing well and encourage their users to adopt other libraries to do other stuff. Choice is a good thing.
> It is not a fully standalone GraphQL server that a client developer could use to start manipulating and querying data.... The only “backend” we have targeted for this early preview are in-memory stubs in test cases.
> To that end the target audience is not the client developer, but those who have or are actively interested in building their own GraphQL implementations and tools.
I guess I'm kind of happy that FB are releasing something regarding GraphQL since introducing it in February. I just thought they got busy with React Native and forgot about everything else they hyped up back in February.
> You can have less plea bargaining and more court overhead, or you can have more plea bargaining and fewer delays for trials.
That sounds like a classic false dichotomy. How about less plea bargaining and more resources for the courts so they don't have require massive delays to deliver justice.
I doubt you'd feel the current system was just if you experienced what Browder went through. How about a little empathy.
Thanks for reminding me about lobste.rs. Last time I checked it out there weren't many comments which didn't inspire me to leave a comment. My favorite part of HN was the potential discussions to be had and its great to see lobste.rs now has more comments than what I used to remember.
Odd, I was sure I had a lobste.rs account but it says my username is invalid. Do you have an invite available?
You don't need another framework to build apps with React. But you will need several libraries as React isn't "kitchen sink" type framework like Ember and Angular.
In my React-based apps, I typically include react-router for routing and request or superagent for ajax calls. You can also include a Flux-inspired library if you're into that sort of thing.
Immutable.js is a project also from FaceBook that brings immutable data structures to your JS applications including those using React.
Since Clojurescript compiles down to JS, wouldn't it be possible to use Immutable.js and a slightly different app design (a single Flux Store for the entire app) to get the same benefit of using React with Clojurescript?