21–30 of 117 posts
Earlier quoted context omitted.
But the api is trying to simulate immediate mode using DOM
That's called an "abomination". The advantage of immediate mode is not storing a DOM. If you write immediate-mode code but it stores a DOM anyway then it's the worst of both worlds.
Earlier quoted context omitted.
That's called an "abomination". The advantage of immediate mode is not storing a DOM. If you write immediate-mode code but it stores a DOM anyway then it's the worst of both worlds.
How would you do layouting without a tree structure in place? Not really sure what you're getting at here
https://joeldare.com/why-im-writing-pure-html-and-css-in-202...
Earlier quoted context omitted.
Framework, not language. And framework choice still matters.
So do programming languages, fwiw. The argument of "we have Fable, X doesn't matter anymore" is a severe case of delusion.
E.g. Just always use Rust instead of Python.
unlike many of the commenters, I found this pretty nice and educational, there are full stack developers who cannot write anything outside React and do not even understand why React was created in the first place
> The only potential issue with immediate mode is performance, since we need to re-render the entire UI on every state change. How this made it to HN front page?
I think the author is saying a potential issue of a vanilla implementation of immediate mode. The following text explains that there is already many optimizations for this
And you (pedro_movai) == the author? So you are saying that potential issue? Sorry, technically you are right that the author is saying that but I got confused with you referring to yourself in third person. Nothing wrong with it. Just want to confirm if you're the author.
I think React is overused, and I'm happy to see people support alternatives.