Signals are a way of expressing state that ensure apps stay fast regardless of how complex they get. Signals are based on reactive principles and provide excellent developer ergonomics, with a unique implementation optimized for Virtual DOM.
Beyond Signals, by Ryan Carniato
GitHub - creativecommons/cc-signals: CC signals is a framework for a simple pact between those stewarding data, and those reusing it for AI development. CC signals provide a set of shared ground rules for an AI ecosystem that is mutually beneficial.
CC signals is a framework for a simple pact between those stewarding data, and those reusing it for AI development. CC signals provide a set of shared ground rules for an AI ecosystem that is mutua...
Signals: Toward a Self-Improving Agent | Factory.ai
Traditional product analytics tell you what happened. Session duration, tool calls executed, completion rates. But they...
Pretext Does What CSS Can't — Measuring Text Before the DOM Even Exists | HackerNoon
Cheng Lou's Pretext library measures multiline text height without touching the DOM — unlocking layout capabilities CSS has never been able to offer.
Prefab: implementing advanced behaviors using pixel-based reverse engineering of interface structure
The rigidity and fragmentation of GUI toolkits are fundamentally limiting the progress and impact of interaction research. Pixel-based methods offer unique potential for addressing these challenges independent of the implementation of any particular ...
Inertia.js - The Modern Monolith
Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
Interfaces › Cheat Sheet
A list of tips, improvements and best practices that quickly make your interfaces better.
Contral — The IDE That Teaches While You Build
Vibecode at full speed and actually understand what you ship. Build Mode + Learn Mode (Java). Stop being a copy-paste developer.
Our interfaces have lost their senses
We programmed them by punching cards, plugging in wires, and flipping switches. Programmers walked among banks of switches and cables, physically choreographing their logic. Being on a computer used to be a full-body experience.
Instrumental interaction: an interaction model for designing post-WIMP user interfaces
Although the power of personal computers has increased 1000-fold over the past 20 years, user interfaces remain essentially the same. Innovations in HCI research, particularly novel interaction techniques, are rarely incorporated into products. In this ...
Effect – The best way to build robust apps in TypeScript
Effect is a powerful TypeScript library designed to help developers easily create complex, synchronous, and asynchronous programs.
Solid 2.0 RC
Anti-patterns | Impeccable
37 deterministic detection rules that flag the visible tells of AI-generated interfaces and common quality issues. Used by npx impeccable detect and the browser extension.
NEAR Intents | Simplifying Web3 Interactions
NEAR Intents let users and AI agents define what they want to do—NEAR handles the rest. A new framework for seamless, multichain execution without complexity, powered by solvers and Chain Signatures.
Good news! I don't need callbacks to implement signals, between components. I can use streams, which are upcoming in WASI 0.3.
Holobrine
>wants to make a UI engine centering wasm instead of JS >wants to use component model >needs callbacks to implement signals >WASI does not support callbacks because of JS scope chains >wasm does not free us from JS, sad