clintonwoo

I had a bitcoin wallet application on my PC. Then joined a mining guild to smooth out the BTC income. Then did the math and I was breaking even on it with the cost of electricity and it was equivalent to just stealing electricity from my parents.

So I left it and forgot about it. And later the mining guild ended up closing so I lost the BTC.

This is exactly the same thing that goes through my head. We could really just fast forward or rewind time and events were always going to happen that way if we could understand the circumstances.

This is a very interesting read. I wish it was longer so I could keep reading more on the topic. I really want to give Austin a visit.

I like VS Code. Been using it for a few months now. Would be nice if it started up faster though. Sometimes I still use sublime just to quickly open a single file.

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.

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.

What put the nail in the coffin to Relay for me was watching a talk by the dev team where they said they don't want to create proper documentation because they feel like that's creating a contract with the community to support the API. It's somewhere on YouTube sorry I can't find it now.

It's using the magic of Google Slides if you can believe it. They have a lot of nice information modeling shapes.

Yes that's true but the page doesn't get cached so in that regard there's still lots of room for real world performance improvements :)

Nothing is being served on a CDN, nor even being cached. It's just a demo running on Google Cloud with Kubernetes/Docker.

Props to Facebook! A wise move given recent community sentiment against Facebook OSS. I will be glad to continue using Facebook OSS software.

In a GraphQL schema you can define resolvers which are functions that retrieve/transform the data before returning it. It works quite well so it doesn't matter much what shape the data of your backends are in.

Thanks for the feedback. It's currently mirroring the HN data in memory and not using it's own database. Any writes would be stored temporarily on one server. Also I'd be worried about people inputting credentials on a demo system. Nevertheless it's on the todo list in some form! edit: I'll probably end up making it work client side only for demo

You can use GraphQL for basically any Web Service endpoint. It's a way to specify what data you want the endpoint to return without writing custom endpoints for different use cases. Write the schema, define how to retrieve the data then make the queries to the GraphQL Server. It's like a more optimized version of RESTful APIs.

Hi, I am the developer of this project. I think the community could use more realistic examples of how to set up a project using GraphQL so I made this. You can use it as a boilerplate to structure your projects. Let me know what you think!

I'm currently working on a new open source project: https://github.com/clintonwoo/hackernews-react-graphql

I moved to the US recently so using it to show my skills to employers seeing as I've been working on entrepreneurial things while traveling. I actually found your post while browsing through my clone of Hacker News! I also have a business Shave Like A Boss which sells traditional shaving equipment: https://www.shavelikeaboss.com.au/

I definitely recommend working on a real idea for a project as you will be able to use it for something in the future.

Hi, I am the developer of this project.

It's mostly working now so I'm posting it to HN to see what people think. The app does server side rendering making a GraphQL request to fetch the data and client side rendering using GraphQL requests too. Using Next JS it gets a bunch of benefits including code splitting and prefetching page assets.

I hope you can use the project as a starting place for your own as a boilerplate or to help you structure your own projects! Let me know what you think. PS: I made an architecture diagram in the readme to help explain.

Hey mate thanks for the kind words. I think you may be right, I'll take your advice.

Thanks for the feedback. I think I'll work out where the project is going to pull data from then host it as a demo. Also need to work out where it will store data (in memory, or couple it to a db).

Currently the easiest way to see it is to run this long command in terminal: git clone https://github.com/clintonwoo/hackersnews-react-graphql.git && cd hackersnews-react-graphql && npm install && npm run dev

Hi, I am the developer who started this project. Please let me know any comments, feedback, ideas or issues you have with the project. It is a work in progress (WIP) so I'm looking more for comments about structure, code design etc.

Please see the project README.md. Pull requests are welcome. I think this could be a valuable community project to demo a slightly larger app using React, Apollo, GraphQL and other web projects.