Live data from Hacker News

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

qitejs.qount25.dev

161–168 of 168 posts

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

#161
post #14

I'm starting to wonder whether reactivity (not React specifically) was the originally sin that led to modern UI complexity. UI elements automatically reacting to data changes (as oppposed to components updating themselves by listening to events) was supposed to make things easier. But in reality, it introduced state as something distinct from both the UI and the data source (usually an API or a local cache). That int…

I’ve written about how Svelte, Vue, and Solid are all reactive and share common pitfalls due to their reactive solutions. My theory is that they all cause worse bugs than they prevent. https://crank.js.org/blog/why-be-reactive/

Compared to what? I mean, what's the alternative for an interactive app?

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

#162
post #14

I'm starting to wonder whether reactivity (not React specifically) was the originally sin that led to modern UI complexity. UI elements automatically reacting to data changes (as oppposed to components updating themselves by listening to events) was supposed to make things easier. But in reality, it introduced state as something distinct from both the UI and the data source (usually an API or a local cache). That int…

The original sin wasn't reactivity. It was putting state in the wrong place. Making the client state heavy. It's been downhill since then. Now you need to duplicate state handling between your frontend language and your backend language. Which leads to "isomorphic" backends seeming like a good idea.

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

#163

Earlier quoted context omitted.

Isn't that what reactive ui trying to achieve? To only have a render function and have ui state sync according to the data?

Games do not sync data, they literally say what should be drawn on the screen, from scratch, 60+ times per second. They are in control of the entire process. They do not need to deal with DOM manipulation overhead because there is no DOM.

Yes, in web to always draw from scratch, it would be slow, therefore exists reactive UI, so people can program like drawing from scratch but less slow.

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

#164

Earlier quoted context omitted.

As much as we like to think of ourselves as rational beings, emotions are still a very large part of our decision making process. I didn't build Qite because I hate React, I built it because I knew exactly how I wanted things to work. But I do hate React and it's part of why I knew exactly how I wanted things to work.

> As much as we like to think of ourselves as rational beings, emotions are still a very large part of our decision making process And yet, plenty of people all around the world are able to get traction for their products without mentioning the hate of another. > I didn't build Qite because I hate React, I get that React being the most popular front-end framework means it's going to get it's fair share of criticism,…

I dislike React because it’s large, slow, and completely unnecessary. If I can write a spa that both 10x faster and 10x smaller without it then why would I bother with React? That isn’t any kind of syndrome. It’s me not wasting my time on vanity bullshit.

I really think autism has a lot to do with the necessity of large frameworks. They provide a vanity layer to hide behind for people who cannot introspect and cannot measure.

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

#165

Earlier quoted context omitted.

> As much as we like to think of ourselves as rational beings, emotions are still a very large part of our decision making process And yet, plenty of people all around the world are able to get traction for their products without mentioning the hate of another. > I didn't build Qite because I hate React, I get that React being the most popular front-end framework means it's going to get it's fair share of criticism,…

I dislike React because it’s large, slow, and completely unnecessary. If I can write a spa that both 10x faster and 10x smaller without it then why would I bother with React? That isn’t any kind of syndrome. It’s me not wasting my time on vanity bullshit. I really think autism has a lot to do with the necessity of large frameworks. They provide a vanity layer to hide behind for people who cannot introspect and cannot…

> I dislike React because it’s large, slow, and completely unnecessary.

You're personal opinion is irrelevant to the point I'm making. And that's exactly my point. For whatever reason people can't stop talking about their dislike for it. Going so far as to literally have it be your framework's tagline.

You can't even read a comment about Svelte without their need to bring React up.

> I really think autism has a lot to do with the necessity of large framework

No it's because the needs of the web have dramatically changed in the last 20 years. That's why people reach for things to help them build front-end apps. It's almost comical how different it is.

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

#166

Earlier quoted context omitted.

I’ve written about how Svelte, Vue, and Solid are all reactive and share common pitfalls due to their reactive solutions. My theory is that they all cause worse bugs than they prevent. https://crank.js.org/blog/why-be-reactive/

Compared to what? I mean, what's the alternative for an interactive app?

Manual refresh(). This is something Crank does, and other frameworks like the new Remix one is picking it up as well. Being explicit has its advantages.

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

#167
post #112

Earlier quoted context omitted.

Is this a satire thing or will it really be remix3? Didnt they just rebrand to react router FROM remix??

No, I'm serious. The previous Remix was rebranded into React Router. Remix 3 will not use React and will apparently not use reactivity either. https://remix.run/ There was a presentation last year: https://www.youtube.com/watch?v=iZl0IKj0HHc

I’ll be darned. Too bad it will become abandonware most likely given the authors history lol
Post reply on HN