My link of the week is ScriptC. I really like the idea of taking the statically compilable part of TypeScript and running it in a fast, small environment without carrying a full JavaScript runtime everywhere. The coverage report and explicit dynamic tier make the trade-off visible, which is much more interesting than pretending all TypeScript is equally static.
News
A two-week reminder for the annual web game competition where the entire entry must fit within 13 KB. This year's jam begins on August 13 at 13:00 CEST, when the theme is revealed, and runs through September 13. Enough time to warm up the tiny asset pipeline and start deleting bytes.
Article
Elastic Security Labs analyzes a Contagious Interview campaign that distributed working, backdoored coding challenges to developers. Base64 payload fragments were hidden in comments across innocent-looking SVG flags, reassembled by JavaScript, and executed on server startup; the resulting malware stole browser credentials, wallets, and files while installing remote-access and clipboard-stealing capabilities. A sharp reminder to treat interview repositories as untrusted code and inspect them before running anything.
Library&tools
TypeScript-to-native compiler that turns its statically supported tier into small executables without Node, V8, or another JavaScript engine. The boundaries are unusually explicit: a coverage report shows what compiles natively, `--dynamic` can embed a roughly 620 KB engine for npm or dynamic code, and unsupported constructs fail with a diagnostic instead of being silently miscompiled. The published hello-world example is about 320 KB and starts in roughly 4 ms.
Interactive framework chooser that ranks 18 frontend options against your priorities: performance, maintainability, bundle size, build time, ecosystem, scalability, learning curve, tooling, stability, and viability. It combines benchmark results with source, download, and community data, making it a useful way to turn "which framework?" into a wider comparison instead of defaulting to React by habit.
The same application implemented across React, Angular, Svelte, Vue, Solid, Qwik, Lit, Astro, Vanilla JS, and several more, then compared on runtime performance, bundle size, build and HMR speed, memory, source complexity, and community health. Benchmarks run nightly against current framework versions, and the raw and historical results are downloadable—good evidence for exploring the field, even if no benchmark can choose an architecture for you.
Ai
Persistent accessibility context for AI coding agents, organized around an 11-rule behavioral contract, WCAG-linked compliance profiles, and 21 lazily loaded implementation guides. Point an agent at the core file—or pin it inside the repository—to make semantic HTML, focus management, announcements, and platform-specific accessibility part of generation from the first edit rather than an audit at the end.
A staff-engineer control layer for coding agents that routes only the architectural constraints relevant to the file being edited, then requires verification proportional to the change. It supports Codex, Claude Code, Cursor, and OpenCode, and backs the idea with reproducible case studies. Interesting attempt to improve agent code quality without turning one giant repository prompt into the source of truth for everything.