- From: Andrea Giammarchi <notifications@github.com>
- Date: Fri, 15 Apr 2022 14:33:33 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/issues/891/1100423418@github.com>
DOM diffing is what everyone uses these days to make anything on the Web, because it's behind every single library, utility, framework, out there, because lists, baskets after buying, calendars, anything dynamic, needs to update their view without trashing their content all over all the time ... on my side, I've also created and investigated all possible algorithms, including: * [Levenshtein distance](https://github.com/WebReflection/majinbuu#majin-buu) based DOM diffing * [E.Meyers's O(ND) Based Diffing Algorithm](https://github.com/WebReflection/speedy-myers#readme) * and ultimately, [udomdiff](https://github.com/WebReflection/udomdiff#readme), passing through [many others](https://webreflection.medium.com/the-web-smallest-dom-diffing-library-5b69ac4d1f4d), including list-diff, snabdom, stage0, spect, and heckel, but I am sure there are more, including petit-dom attempts, and literally every other utility out there I believe if we had a primitive for this case, we'll be innovating on other areas, instead of keep solving the same thing we needed to solve since AJAX existed 10+ years ago, but I am sure all these attempts used in the real-world aren't a good-enough evidence everyone would benefit from native diffing, right? > counterproductive to keep repeating the same discussion every 2-3 years it's also very counterproductive to keep ignoring developers voice for all these years, imho. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/891#issuecomment-1100423418 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/dom/issues/891/1100423418@github.com>
Received on Friday, 15 April 2022 21:33:45 UTC