no-virtual-dom icon indicating copy to clipboard operation
no-virtual-dom copied to clipboard

Short description on how other frameworks handle the same problem

Open kodedninja opened this issue 5 years ago • 4 comments

I really like the idea of collecting these awesome frameworks! I think it would be useful to have a short description on how do they handle updates, as usually this is done very differently.

For example, while in Choo the logic is very similar to what vdom uses, but with real Nodes, Radi uses a totally different approach.

✌️

kodedninja avatar May 22 '19 13:05 kodedninja

That's a terrific idea! What do you think would be the most appropriate way to show this? Just a note next to each link? A link to the source of the explanation (assuming one exists)?

achou11 avatar May 22 '19 13:05 achou11

Hmm... Personally I would like to see a brief description next to the framework and then optionally a link to a more specific explanation. This way there's a nice overview of the different possibilities, but you can also read about the ones you like easily (and also, maybe it helps seeing for people new in this field why isn't this a simple problem and why are there so many different ways to solve it).

But of course, it wouldn't be good idea to bloat the readme. 😄

kodedninja avatar May 22 '19 13:05 kodedninja

Hm yeah I think a short description with an accompanying link is a good way to go. We'll try that and see how it works out as we add more projects :)

achou11 avatar May 22 '19 14:05 achou11

Actually, I've been on a quest trying to understand why "no virtual dom" is so special for svelte - but I'm a bit at a loss seeing the distinction between vdom and real dom frameworks.

That article "the virtual dom is pure overhead" really doesn't give good technical indication what's happening besides a lot of marketing.

Isn't any type of JS framework containing logic that writes to the real dom given some circumstances. I understand that in react's case, that is called the "virtual dom". But somehow svelte also has to keep track of the real dom and eventually write some state. Maybe it's not replicating it 1:1, but surely it also creates a conceptual copy.

I'm interested in real dom frameworks and I'd appreciate finding an article that highlights the differences on a technical level and defines what "virtual dom" means.

TimDaub avatar Nov 15 '21 07:11 TimDaub