nodkz

Performance problems in Apollo Client v2, v3 and Relay. Why we need a new GraphQL Client?

Both Apollo Client and Relay provide great State Managers for storing GraphQL responses with component updates on data changes. Under the hood they are using Cache Normalization that reduces data redundancy. More details can be found here for Apollo and here for Relay. This Normalization is a killer feature for Modern Web Apps - it helps to keep in sync displayable data of some entity in different parts of your application. But this Normalization has performance problems on big data sets.

Cache Normalization in Apollo Client 2 and Relay

Apollo Client was originally created as lightweight alternative of Relay. Apollo re-implemented basic functionality keeping in mind developer experience and bundle size. But conceptually Apollo Client 2

zstix

1. Continuous Integration

1. Have the required tests passed?
2. Has the build completed successfully?
3. Does the submitted code meet linting requirements?
4. Have all the other required checks passed?

2. Code Style

1. Are variables and function names consistent with the code base?
2. Are variables and function names clear and accurate?
3. Are the files located in a reasonable location?

zstix

// Generates a simplified kanban board view for a Github project.
// Author: Zack Stickles
//
// Requires a GH_TOKEN is set in the environment (with org and repo read permissions).
/*

*/

const { Octokit } = require("@octokit/rest");

prologic

Learn Go in ~5mins

This is inspired by A half-hour to learn Rust and Zig in 30 minutes.

Basics

Your first Go program as a classical "Hello World" is pretty simple:

First we create a workspace for our project: