Skip to content

Instantly share code, notes, and snippets.

View jpuri's full-sized avatar

Jyoti Puri jpuri

View GitHub Profile
@veekaybee
veekaybee / normcore-llm.md
Last active April 27, 2025 07:05
Normcore LLM Reads

Anti-hype LLM reading list

Goals: Add links that are reasonable and good explanations of how stuff works. No hype and no vendor content if possible. Practical first-hand accounts of models in prod eagerly sought.

Foundational Concepts

Screenshot 2023-12-18 at 10 40 27 PM

Pre-Transformer Models

@acdlite
acdlite / coordinating-async-react.md
Last active June 17, 2024 11:56
Demo: Coordinating async React with non-React views

Demo: Coordinating async React with non-React views

tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.

A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.

But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.

How do we solve this with React?

import is from '../../plugins/is';
const minWidth = 'min-width';
const maxWidth = 'max-width';
const query = (size, measure) => {
return `@media (${measure}: ${size}px)`
};
const matchMedia = (val) => {
import variables from './variables.config';
import Color from 'color';
const debuggingColors = [];
const randomColor = () => {
return '#' + (Math.random() * 0xFFFFFF << 0).toString(16);
};
const getColor = (color) => {