Hacker News new | ask | show | jobs
by bartwaardenburg 83 days ago
The fields/flags state model is a nice idea, having structured values separate from boolean state is something I haven't seen in other frameworks. How does this compare to Alpine.js or htmx in practice? They're in a similar space (no build, SSR-first) but I'm curious what made you go with a new framework rather than building on top of those?
3 comments
dleeftink 83 days ago
Think Xstate[0] machines are a little more intuitive than the conditional value structuring displayed here in the example, but it is an interesting idea indeed.

[0]: https://github.com/statelyai/xstate?tab=readme-ov-file#super...

link
usrbinenv 83 days ago
Alpine/htmx are great, but they're more "sprinkle behavior on HTML" tools. Qite is closer to a structured component system: explicit events, a state engine, and a consistent way to wire parts/fields/children together without ad-hoc glue.

You can build similar things with Alpine/htmx, but once things grow, you end up reinventing structure. Qite just bakes that in from the start.

link
aledevv 83 days ago
I agree, I hate unnecessary hypercomplexity.

Most of the time, it's enough to build in a simple, clean, and lightweight way. Just like in the old days. Your server's resources will also thank you. Furthermore, the simplicity of web pages is also rewarded by search engines.

If it were up to me, I'd build sites exclusively in .md format :)

link