News for hackers. Stuff that matters.
Re:TodoMVC App Written in Vanilla JavaScript by anonymoushn on Saturday May 07, 2022 @09:43AM (#31294369)
it sounds sort of wild to expect there to be diffing! why do you have to generate a whole copy of the stuff instead of just telling the browser what changes to make? bonus: the existing apis instead of one that don't exist yet.
Re:TodoMVC App Written in Vanilla JavaScript by Philip-J-Fry on Saturday May 07, 2022 @10:11AM (#31294612)
Because it can be automated? Every app that doesn't do this is just implementing the diff by hand, e.g. on this event delete this element, update this element, add CSS class to this element, etc. When the UI gets complicated you have to maintain this all yourself and it's a pain. Multiple event listeners between components to say something has happened.

It makes sense to be able to describe what you want to achieve and to let the browser determine how to get there in the most efficient way.

If the browser could do this it would make a tonne of JS code so much simpler. There's a lot that goes into making sure that there's no unnecessary DOM updates because it's just slow.

I don't write assembly and move things between registers by hand, I write a function and the compiler decides the most efficient way of doing it. UI should be the same way, I say what I want to happen and the browser decides how to get there.

Re:TodoMVC App Written in Vanilla JavaScript by bobbylarrybobby on Saturday May 07, 2022 @10:32AM (#31294804)
Yes, but there are ways to accomplish this automation without diffing. Svelte does this by statically wiring up the data dependencies in your app when it builds, and then at runtime making exactly the changes to the DOM that it needs to based on the information it had at build time. No need to diff.
Re:TodoMVC App Written in Vanilla JavaScript by Philip-J-Fry on Saturday May 07, 2022 @11:01AM (#31295053)
The point is that A) that's a framework and B) that requires you to compile Svelte files.

If you want to write declarative UI in pure JS then you need the browser to do these DOM optimisations for you, and diffing the changes is the way to do that.

Re:TodoMVC App Written in Vanilla JavaScript by 5560675260 on Saturday May 07, 2022 @10:32AM (#31294802)
> When the UI gets complicated you have to maintain this all yourself and it's a pain

This is also something that can be automated by a framework. Check out https://svelte.dev/blog/virtual-dom-is-pure-overhead

Re:TodoMVC App Written in Vanilla JavaScript by Philip-J-Fry on Saturday May 07, 2022 @10:58AM (#31295023)
Yes... but that's the exact argument I'm making here. Unless you want to go through that pain, you need a framework.

Whether that's Svelte without a VDOM or React with a VDOM. The entire point of these frameworks is that you can write complex UI in a declarative way. They both exist because writing it declaratively in pure JS leads to performance issues. But there's nothing stopping the browser implementing something that does this optimisation for you.

Re:TodoMVC App Written in Vanilla JavaScript by recursive on Saturday May 07, 2022 @11:02AM (#31295057)
I find the "pain" to be drastically overstated. See this HN post.
Re:TodoMVC App Written in Vanilla JavaScript by noahtallen on Sunday May 08, 2022 @02:44AM (#31301888)
I mean, it’s clear that with a single view, it’s possible to manage this without too much trouble. But next to no apps are single views. And any project that has multiple people working on it is going to have multiple views and features which all interact in interesting ways. It’s definitely not overstated. Try writing a moderately involved app yourself in plain JS! It does get to be a pain, I’ve done it! By the time you finish, you’ll have likely created some level of abstractions, and invented yourself a nice new JS framework for yourself ;)
Re:TodoMVC App Written in Vanilla JavaScript by Bilal_io on Saturday May 07, 2022 @09:57AM (#31294480)
Diffing seems necessary when your UI gets complicated to the level that a small change requires a full page re-render. However, I don't think this is necessary for at least 95% of the websites on the internet.
Re:TodoMVC App Written in Vanilla JavaScript by dymk on Saturday May 07, 2022 @09:59AM (#31294508)
Diffing is exactly what you need to do (barring newer methods like svelte) to figure out what to tell the browser to change. The vdom tree is much faster to manipulate than DOM nodes.
Re:TodoMVC App Written in Vanilla JavaScript by recursive on Saturday May 07, 2022 @11:03AM (#31295074)
But you can't see those changes until the actual DOM changes as well. It's only because of react's insistence that mutation is evil that this became a problem. You could just directly update the thing you wanted to and just skip the whole diff thing.
Re:TodoMVC App Written in Vanilla JavaScript by dymk on Saturday May 07, 2022 @01:27PM (#31296638)
No, the reason React has a VDOM is because the DOM is slow to update, compared to manipulating javascript objects. It's worthwhile to calculate the list of minimum updates ahead of time rather than using the DOM as the source of truth.

Not sure where you think mutation comes into play here, that's an orthogonal concern—you can have an API that mutates some internal representation of a VDOM, and it's still faster than manipulating the DOM directly.

Re:TodoMVC App Written in Vanilla JavaScript by recursive on Saturday May 07, 2022 @03:15PM (#31297612)
In order to achieve immutability, large chunks of state have to be cloned whenever a single value changes. This sometimes causes a whole new DOM node to be created during reconciliation. React encourages you not to think about it too much. But some nodes can't be replaced. Like canvas or anything contentEditable. It's not orthogonal. It's a direct consequence of the design philosophy.