Johnson Chu johnsoncodehk

These are some notes on the performance work that went into alien-signals. I'm sharing them not as a definitive guide, but as a log of a few key discoveries. The hope is that some of these findings might be useful to others tackling similar problems in high-performance JavaScript.

The Origin: Push-Pull-Push

My journey into the depths of reactivity performance began with Vue. I was trying to solve a specific problem in Vue 3.4: even if a computed's value didn't change, it would still trigger downstream computations and effects. This seemed inefficient. My attempt to fix this resulted in a pull request (vuejs/core#5912) that, after a year of discussions, was eventually merged. This PR introduced the Push-Pull-Push model to Vue 3.4, a model also adopted by libraries like reactivity.

For a time, I thought this was near-perfect. Then I saw the plans for Vue 3.5, which adopted a doubly-linked list but also moved to a pure pull-based model. I was still convinced

Running ESLint rules at 16× speed in TSSLint

On Dify web/ (5860 .ts / .tsx files), running one type-aware rule:

	Wall (min of 3)	Peak RSS
ESLint Linter	25 s	7.0 GB
TSSLint 3.1	1.5 s	3.75 GB

Native linters (Rust's Oxlint and the like) hitting 10× is normal — that's the cross-runtime gap. JS-vs-JS usually lands at 1.5-3×. This 16× is the same V8, the same ESLint rule source, the same ESTree shape — the gap is all architecture. 3.1 is a full rewrite of @tsslint/compat-eslint (the compatibility layer that lets stock ESLint rules run inside TSSLint). Bench: tsslint-dify-bench.

To adopt: copy the block below into your ~/.claude/CLAUDE.md.

## How to decide what to do

Judge every piece of work by whether it **should** be done — is it correct, is the current state wrong or inconsistent, does it serve the goal — and **never by ROI, cost, effort, or "is it worth it."** Do not label a known-wrong thing "low-value," "marginal," "an edge case," or "not worth it" to justify leaving it unfixed; reasoning by ROI is exactly what keeps work mediocre. ("The reference / competitor also gets it wrong" is a *gap* argument, not a correctness one — it never makes a wrong thing acceptable.)

The only valid reason to stop short of doing the right thing is that it **provably cannot** be done — a demonstrated limit of the model or tools, not an assumed or cost-based one. "Hard," "heavy," "expensive," or "a lot of work" is never a reason to stop; "proven impossible / blocked" is. When unsure which it is, find out — try it, measure it, prove it — before deciding, and never declare a limi

delegate-flash 安裝引導

這份文件是寫給 Kimi Code 主代理看的安裝程式，不是給人讀的教學。用戶把 gist 貼給你，即表示授權你完成下列安裝。每步先做一句說明再動手；凡寫到工作目錄以外的位置（skills 目錄、config.toml、shell rc），動手前各自確認一次。

步驟

安裝 skill 檔 用戶貼的 gist 網址形如 https://gist.github.com/<owner>/<id>。FetchURL 拉 https://gist.githubusercontent.com/<owner>/<id>/raw/SKILL.md（失敗就改 curl -L），Write 到 ~/.kimi-code/skills/delegate-flash/SKILL.md；同法把 INSTALL.md 也帶回同目錄，日後參考用。

	import type config = require('@tsslint/config');

	import path = require('node:path');

	export function create(): config.Rule {
	return ({ typescript: ts, sourceFile, reportError, languageServiceHost }) => {
	const { noEmit } = languageServiceHost.getCompilationSettings();
	if (noEmit) {
	return;
	}