unknown

JavaScript frameworks are increasingly introducing custom directives like 'use server', 'use client', and 'use cache' that resemble language features but lack standardization. These directives create confusion by appearing authoritative while being framework-specific, leading to portability issues, tooling complexity, and vendor lock-in. The piece argues for using explicit APIs with imports instead of directives, as APIs provide better provenance, versioning, composition, and type safety. Drawing parallels to past ecosystem challenges like TypeScript decorators, it advocates for clearer boundaries between framework behavior and platform semantics to prevent fragmentation.

Directives and the Platform Boundary

Yonatan Paripsky

An important opinion post from the creator of React Query and the well know TanStack about the new “use workflow” and “use step” directives for workflow management by Vercel.

<p>An important opinion post from the creator of React Query and the well know TanStack about the new “use workflow” and “use step” directives for workflow management by Vercel.</p>

<p>Interesting, however personal bias occurs …</p>
