Show HN: I made a better DOM morphing algorithm
8 days ago (joel.drapper.me)
At least I think it’s better, but also I could also be missing something obvious.
8 days ago (joel.drapper.me)
At least I think it’s better, but also I could also be missing something obvious.
I recently turned on View Morphing via upgrading Turbo 7->8 [1] in production and man it really does feel faster. Like a free performance upgrade.
I looked it up on Github and they seem to be using the idiomorph package.
[1] https://dev.37signals.com/turbo-8-released/
I’m curious, what got you interested in solving this particular problem? I.e. what was your specific use case?
Most websites work fine with plain html. If you need something fancier, the world seems to have settled on using React.
I get that this is to let you render html on the backend and then stream it to the site so that JS can update the dom. But why? Genuine question; I’m not saying there’s no good reason.
Both Elixir Phoenix and Ruby on Rails use plain HTML by default but they both support view morphing (phoenix via LiveView and rails via Hotwire Turbo). It really doesn't cost anything to add it. Clicking links with a bit of caching can make it feel near instant the way a (small) SPA does. Adding link prefetching algo on top of the that and it will seem even faster.
If anything it removes a ton of the argument for using React absent maybe a small subset of highly complex UI subcomponents which may need it, but rarely required for a whole SaaS app. Frontend teams just want React so they can use a single tool not because it's the best solution.
> the world seems to have settled on using React.
The world might have, but I personally have not!!! x(
(I don't think the world really has, the same way the world moved on from jQuery at some point :) and jQuery was probably more widespread)
Although the OP created it for SSR, these libraries are handy for SPAs as well.
Rendering the whole DOM tree (instead of VDOMs) is a fast process. The slow part is attaching (committing) elements to the doc. e.g., I have a test of 20,000 elements which takes <30ms to render, while attaching them takes 120ms.
Since the performance is mainly bound to the commit phase, libraries like these (and hopefuly a native API) help for creating simple UI frameworks. For example, a helper such as:
could be used, like:
Here's an example of using that helper:
https://github.com/ericfortis/mockaton/blob/main/src/client/...
I’m doing agentic coding on a bunch of web apps and server side rendering HTML is so much easier than building APIs and React components.
Full page reloads are fine for most CRUD cases. Then layering DOM morphing can be even better UX almost for free
If you read the first 5 sentences of the article you’d see there are at least 3 popular front end libraries that do morphing. I think suggesting the world has settled on anything when it comes to technology is very silly.
*Edit fixed typo.
Wouldn't 'DOM Merging' be a more descriptive term?
Can you see if you can support the input-to-output sync of the examples you see on https://rtcode.io ?
Does your library support the new state-preserving moveBefore method?
Sorry, I was excited to see something newer than diffHTML and asked questions before reading the full article! You do use moveBefore with lots of effort to match elements, which makes Morphlex a very interesting library to try!
I will test your library extensively and update you via GitHub in case of questions/issues!
Thank you for releasing Morphlex!
Is there a website where we can try this out on?