Looks great, thanks for this! Back when I worked with Meteor, Arunoda's work was exceptionally helpful.

The homepage seems to be a bit confusing, I think. You don't have to sign up to read some of the content. There is a small link below the large button: https://learngraphql.com/basics/introduction.

Correction: As sync pointed out, you still need to sign up to access the full content.

You still have to sign up for the 'Start Lesson' button at the bottom of every page.

Ah, that's a bit of a shame.

Guys, this is an activity based course. That's why you need to login.

You can do stuff and get points. This is a good way to learn something. We've prior experience in with our BulletProof Meteor course.

It's a decent course and I appreciate the effort. I'd rather have given my consent to being put on a public leaderboard though.

Looks awesome, but you might want to say this explicitly on the landing page.

I also came here to the comments to ask why I would want to hand over account information on an unrelated service.

why not just save activity info in localstorage?

I did not follow the Meteor course, but my impression was it was trying to get my email address to sell me something later on

Perhaps a short sentence in Gray near "Next Lesson" telling you will never sell emails (or similar) would help

I signed up on mobile (iOS) and it went into a loop

Got it. Will work on it.

Looks interesting. Question: why do I need to sign in with my Github account?

It's an online course, you need to do some tasks in each lesson. And you get points.

That's why you need to login with GitHub. See more on this: https://news.ycombinator.com/item?id=10384683

Don't know why people would downvote this. The permission this site is asking is only email address associated with Github. As someone who is always logged in with Github, this saves me from creating another account associated with my email address.

Well this could be done without having me entered into a public leaderboard and having some kind of "who's is bigger" contest made out of it.

I very much would prefer the content to be accessible without this ego-bolstering crap.

Sorry, but local storage or a cookie dropped would suffice. Why should this introduction be in any way tied to me or my Github profile?

It may be so easy, to just log in with Github. But for me this just kills it. I assume, that a lot of people think alike - that might be the reasons for downvotes.

Interesting how you consider it ego-bolstering. Can't you just ignore the leaderboard?

It seems a lot of effort goes into making this tutorial. The guy working on it seems to be running a business. Although it can be done without requiring a sign-up as you said, I also understand how the author would like more people to sign-up, follow the competition, and potentially use his company's service.

Writing good tutorial is actually pretty hard and time-consuming. Just making it open and not getting any benefit out of it is not a sustainble business.

Well I could ignore it, if it were not tied for ever to my github account. Something some future employer might have a look into. And maybe I suck at this thing and...

... well you get the point. If I want to have it on my resume, I will put it there. If not it should not be findable, because I once looked into it, but maybe didn't have the stamina to push through.

So maybe "ego-bolstering" was a bit harsh. But non the less - this requirement just killed it.

Well said.

I don't even have a github account (unheard of on HN I know), so the requirement to create one to use the site essentially means it goes in the bin.

Or you could just create a github account...

that people would defend having to log into a social media account to read a tutorial on a database language made me physically ill

I had to swallow it (just bile)

Get well soon. Also, get over it soon.

Looks fantastic, thanks! FYI I shared this in Slack and the preview showed up like as "Learn How to Build Fast and Efficient Meteor Apps" - screenshot: http://url.brentvatne.ca/VYvi.png

Good call. Working on it :)

Awesome to see the Kadira team branching out beyond Meteor-only content, can't wait to check this out!

Sorry for my ignorance about the project, GraphQL looks awesome in terms of flexibility while developing and saving network traffic, but I have a question related to how API backend will work with GraphQL.

If storage was some kind of NoSQL and stores everything as one huge JSON, then we can filter out data while retrieving, but what would happen if data storage is RDBMS? Are we going to do multiple joins to retrieve data?

seems GraphQL work really well with graph databases, but if you have 2-3nesting in GraphQL query, then you need to do multiple big joins on the server side

Yes, you could end up with multiple big joins. The advantage is that you're at least only doing a single query for those joins. What would be worse is performing joins on the client and doing three separate queries to get the data you need.

Also, keep in mind that this is a query language and not an API spec. If you want to allow clients to perform massive joins then GraphQL will facilitate that, but that's your decision to make. Ultimately you still need to decide what clients can and can not query.

Facebook made it, so even though they are using an RDBMS they aren't doing any joins. They use MySQL just as you would a nosql datastore in that to "join" data they are doing multiple queries and stitching the results together manually.

The team at Kadira is great at diving into technical subjects and making fun and easy to follow learning materials. I loved Bullet Proof Meteor, I'm looking forward to learning GrapgQL through this new course.

How does this compare to Falcor? Can they be used together or ar they competing technologies?

Falcor is based on top of REST. It's core is on top of the client side.

GraphQL is different and trying focus on the API end. (You can think it's trying to replace REST). GraphQL's client side part it Relay for now. It's somewhat complex compared with Falcor. But, I believe we can have a easy to use React independent client for GraphQL.

many many thanks , its really awesome .

what use case is there for graphql? and what does meteor have to do with it?

GraphQL basically allows to build your backend as a well defined API. Then, you can query it from anywhere. It has a good query language and some nice tools like GraphiQL - https://github.com/graphql/graphiql

Meteor is a full stack. It has no direct relationship(or cannot compare with) GraphQL. Meteor also a realtime framework, but GraphQL does not address realtime aspects (yet).