React Compiler and Beyond: Capability Boundaries of Compiler-Driven UI Frameworks

Bottom line first: React Compiler is a major step forward, but it optimizes React's expression and render costs within React's runtime contract. Compiler-first fine-grained frameworks like Fict pursue a different objective: move more update routing to compile time, then execute updates through dependency propagation at runtime. This is not a winner-takes-all debate. It is an engineering trade-off across different objective functions. Fict Repo: https://github.com/fictjs/fict 0. Scope and Rigor To avoid slogan-level comparisons, this article uses strict boundaries: It compares two technical routes: React + React Compiler (preserving React semantics) Compiler-first fine-grained (using Fict as the concrete example) It separates three layers: Developer experience (mental overhead and ergonomics) Performance model (update path and cost structure) Semantic constraints (effects, lifecycle, error handling, consistency) Claims about Fict are grounded in this repository's implementation and docs