21–30 of 53 posts
Earlier quoted context omitted.
An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves .
I'm not sure if you are you are fucking with me or if i'm just ery stupid.... :(
Can someone ELI5(+) what an isomorphic virtual dom is?
Can someone ELI5(+) what an isomorphic virtual dom is?
Sorry for the confusion I tried to write a title that would fit and guess I missed the mark! What I really mean is a virtual dom implementation that - On the frontend can diff/patch a real DOM node - On the backend can render into an HTML string that you can serve So my intended takeaway with that title was: -> A virtual dom implementation that allows you to write frontend web applications that support server side re…
You did not miss the mark, you did a good job in the limited space you had.
Earlier quoted context omitted.
An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves .
> An isomorphic virtual DOM is much like an inverted-index homomorphic shadow DOM, but instead of using a shadowed mapping they virtualize the original elements themselves. Not sure if this is ironic, but a 5 year old definitely wouldn't understand this!
Earlier quoted context omitted.
damn, this sounds awesome, specially the part about batching renders, much like 'vsync' but for DOM. thank you for the info!
(Ok, before anyone goes running off telling their colleagues about this great new tech: I literally made all of this up on the fly except the batching stuff. That's actually one of two reasons why this whole shadow-DOM-stuff exists. The other is encapsulation. I think this whole thread is a most beautiful demonstration of Poe's law in its original form.)
Earlier quoted context omitted.
damn, this sounds awesome, specially the part about batching renders, much like 'vsync' but for DOM. thank you for the info!
(Ok, before anyone goes running off telling their colleagues about this great new tech: I literally made all of this up on the fly except the batching stuff. That's actually one of two reasons why this whole shadow-DOM-stuff exists. The other is encapsulation. I think this whole thread is a most beautiful demonstration of Poe's law in its original form.)
I think I have some new tech to tell my coworkers about. >;)
can you write an app in just once file and mark what can run in the client and what must only run on the server?
Heads up, there's something already called Percy in the JS space. https://percy.io