not doing a virtual dom should already place it fa...
# compose-webj
jw
06/14/2021, 4:03 PMnot doing a virtual dom should already place it far ahead. a more interesting comparison would be svelte
s
spierce7
06/14/2021, 4:52 PMIt’d be a performance comparison of Virtual DOM vs Gap Buffer, right? https://kotlinlang.slack.com/archives/CJLTWPH7S/p1622564972091000?thread_ts=1622485818.455800&cid=CJLTWPH7S
I can’t imagine that the information stored in a virtual dom is going to be wildly different from the information stored in the gap buffer. I’m assuming that compose is just 1. Storing less information and 2. Storing it in a more efficient way.
I have no idea what I’m talking about of course, but I’d love to see how they compare.
➕ 1
4 Views