PraxisJS – signal-driven front end framework and AI experiment

Name: PraxisJS – signal-driven front end framework and AI experiment
Availability: InStock
Author: mateusgx

by mateusgx·Mar 1, 2026·2 points·0 comments

Visit Project View on HN

AI Analysis

●MidBig BrainShip It

No virtual DOM and decorators over JSX—but Solid.js, Qwik, and Svelte already did this better.

Strengths

•@State/@Prop/@Watch decorators make reactivity visible in code, not buried in hooks
•First-party ecosystem: router, store, animations, devtools avoid fragmentation and wrapper hell
•Fine-grained reactivity with no reconciliation layer means no diffing overhead—theoretically faster

Weaknesses

•Solid.js, Qwik, Vue 3, Svelte all ship signal-driven reactivity maturely; no differentiation here
•v0.1.0 beta in April 2025; competing frameworks have years of production data and ecosystem polish
•Explicit code-first design is a *philosophy*, not a technical breakthrough—Solid proved this already

Post Description

I built PraxisJS, a signal-driven frontend framework exploring what a more explicit and traceable architecture could look like.

PraxisJS started as a personal project. It reflects a single perspective on frontend design, not a committee decision, not a consensus. I wanted to see how far you can push explicitness before it becomes friction.

Most frameworks optimize for writing less. PraxisJS questions that tradeoff. @State doesn’t suggest reactivity, it is reactive, visible in the code. Signals reach the DOM without a reconciliation layer in between (the renderer is still evolving toward that goal).

It also became an AI-assisted experiment, not to automate thinking, but to pressure-test ideas. Some parts came from that collaboration. Some exist because it failed.

v0.1.0 beta, experimental, not production-ready. But the ideas are real.