Live data from Hacker News

Qite.js – Frontend framework for people who hate React and love HTML

qitejs.qount25.dev

1–10 of 168 posts

Re: Qite.js – Frontend framework for people who hate React and love HTML

#2
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?

Re: Qite.js – Frontend framework for people who hate React and love HTML

#4

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?

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 :)

Re: Qite.js – Frontend framework for people who hate React and love HTML

#7

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?

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...

Re: Qite.js – Frontend framework for people who hate React and love HTML

#8

"If you hate react" feels like very bad argument in engineering. Anyway, interesting approach for up to medium pages (not apps!). Totally not replacement for react.

Perhaps a bad argument, but for some people a very compelling one...

Re: Qite.js – Frontend framework for people who hate React and love HTML

#9
post #4

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?

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 :)

[dead]

Re: Qite.js – Frontend framework for people who hate React and love HTML

#10

"If you hate react" feels like very bad argument in engineering. Anyway, interesting approach for up to medium pages (not apps!). Totally not replacement for react.

Why is that a bad argument? The author strongly dislikes React and so wrote an alternative that is radically more simple, which sounds like a perfectly sane argument.
Post reply on HN