Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hacker News Clone Using GraphQL and React

github.com

Post reply on HN
Print view View original

71–80 of 187 posts

Re: Hacker News Clone Using GraphQL and React

#71

Post by turdnagel »

ythn wrote: post #70
zaroth wrote: post #68

The real link: http://www.hnclone.win/ Fantastic resource! The key point of this is it provides working example code to start a project from. Everything is MIT Licensed so that means you get to download it and just start hacking. I would love to see some accompanying video tutorials! Of course people are also free to post their own examples using their own favorite technologies. I would love for 'HN Clone' to become…

> Everything is MIT Licensed Besides GraphQL you mean

Facebook switched it over to MIT last week (along with React): https://github.com/graphql/graphql-js/blob/master/LICENSE

Re: Hacker News Clone Using GraphQL and React

#72

Post by AFNobody »

IncRnd wrote: post #54
cdata wrote: post #44

This is a nice example of the state of the art of a React & Friends stack. Thank you for building it and sharing it. Is it supposed to be completely functional? Login doesn't seem to work for me, at least. After 1.1 MB transferred, I experience subjectively sluggish page transitions and less-subjective FOUC on a recent MacBook Pro and Chrome over fast wifi. The features in this stack are impressive and appealing, but…

Are you saying that you put your regular hacker news credentials into this system?

http://www.hnclone.win/login

If you try to create an account you get an internal server error. I assume that is what the OP means.

Re: Hacker News Clone Using GraphQL and React

#73

Post by Touche »

ng12 wrote: post #13
nodesocket wrote: post #5

Awesome job. This is not a knock on JavaScript in particular, but the amount of brain bandwidth and dependencies to launch a modern web app is getting a bit absurd. I'm turning into that old grumpy hacker who prefers the simple good ole' days of LAMP. :-) React - (UI Framework) GraphQL - (Web Data API) Apollo - (GraphQL Client) Next - (Routing, SSR, Hot Module Reloading, Code Splitting, Build tool uses Webpack) Redux…

I see these kind of posts often. What's a reasonable benchmark? What useful projects have only a handful of dependencies? You could say the same about a project in any language -- it's just more noticeable in the JavaScript ecosystem because best practices are still developing.

news.ycombinator.com which is faster and has 0 js deps.

Re: Hacker News Clone Using GraphQL and React

#74

Post by altano »

whalesalad wrote: post #65

I really dislike the tendency to couple graphql queries with components. Is this idiomatic? If you are comfortable with side effects in your presentation layer i’d much rather manage data at a higher level and have a component request the data it needs from that. As opposed to actually making HTTP requests. What happens when two components used in two totally different areas of a single page need common data? Relying…

Declaring what data your UI binds to is not a side effect, so co-locating GraphQL queries with your component doesn't necessarily introduce side effects. You don't have to co-locate GraphQL mutation queries to your component, you can just have your event handlers (or other mutation-creating events) handled elsewhere in your app.

> What happens when two components used in two totally different areas of a single page need common data? Relying on a cache feels like a hack.

When declaring what data you rely on is as simple as a GraphQL query, it's basically like declaring what data goes in your component. It's NOT like building ORM layers directly into your UI components.

Re: Hacker News Clone Using GraphQL and React

#76

Post by clintonwoo »

whalesalad wrote: post #65

I really dislike the tendency to couple graphql queries with components. Is this idiomatic? If you are comfortable with side effects in your presentation layer i’d much rather manage data at a higher level and have a component request the data it needs from that. As opposed to actually making HTTP requests. What happens when two components used in two totally different areas of a single page need common data? Relying…

It's not really coupling queries with components, only fragments. You can build a query with fragments so the query is definitely decoupled.

If two components used in different areas needed common data that would get pieced together through the fragments. Just depends how you architect your app.

Re: Hacker News Clone Using GraphQL and React

#77

Post by hasenj »

Clicking on comments results in a weird flicker effect where the page appears empty for a split second before being filled with content.

Also, the comment collapse button doesn't seem to work.

Is there really any benefit to implement HN as a JS driven web application? IMO, Hacker News is simple enough such that implementing it as JS-Driven app actually makes it slower than the original.

Re: Hacker News Clone Using GraphQL and React

#78

Post by abritinthebay »

whalesalad wrote: post #65

I really dislike the tendency to couple graphql queries with components. Is this idiomatic? If you are comfortable with side effects in your presentation layer i’d much rather manage data at a higher level and have a component request the data it needs from that. As opposed to actually making HTTP requests. What happens when two components used in two totally different areas of a single page need common data? Relying…

> Is this idiomatic?

Not for React but it's basically the exact idiomatic use case of Relay. GraphQL or React don't require it at all however.

Re: Hacker News Clone Using GraphQL and React

#79

Post by abritinthebay »

whitefish wrote: post #67
whalesalad wrote: post #65

I really dislike the tendency to couple graphql queries with components. Is this idiomatic? If you are comfortable with side effects in your presentation layer i’d much rather manage data at a higher level and have a component request the data it needs from that. As opposed to actually making HTTP requests. What happens when two components used in two totally different areas of a single page need common data? Relying…

So basically you prefer something more along the lines of Model View Controller. Me too. When React was first released it was advertised as “the ‘V’ in MVC”. Unfortunately the developer community took it in a different direction.

How so? It still is exactly that.

You can add additional layers/groupings/couplings but that isn't React doing that...

Re: Hacker News Clone Using GraphQL and React

#80

Post by clintonwoo »

hasenj wrote: post #77

Clicking on comments results in a weird flicker effect where the page appears empty for a split second before being filled with content. Also, the comment collapse button doesn't seem to work. Is there really any benefit to implement HN as a JS driven web application? IMO, Hacker News is simple enough such that implementing it as JS-Driven app actually makes it slower than the original.

Yes the benefit is that you can prefetch other page assets then client render new pages using only GraphQL queries. Download the whole site once and and runs more like an app afterwards.

Perhaps a good alternative to the flicker effect would be to put loading indicators in place of each UI component as it loads so you can see the structure.

Post reply on HN