Hacker GitHub

← All repos

wilsonpage/fastdom

View on GitHub ↗ ★ 6,912 JavaScript

Eliminates layout thrashing by batching DOM measurement and mutation tasks

17 mentions on Hacker News by 11 people: 3 stories, 14 comments · first 2013-10-03 · latest 2023-08-03

Mentions per year 17 mentions · busiest year 2019 (4)
20082026
  1. …that first, before it can return a correct value. This is the reason that libraries like fastdom ( https://github.com/wilsonpage/fastdom ) exist - they help ensure that, in a given tick, all the reads happen first, followed by all the…
  2. …its true that augmenting jQuery with a batcher for performance doesn't seems currently possible? https://github.com/wilsonpage/fastdom
    comment by SemanticStrengh · 2022-05-19 · in Gov.uk drops jQuery from their front end
  3. https://github.com/wilsonpage/fastdom
    comment by SemanticStrengh · 2022-05-07 · in TodoMVC App Written in Vanilla JavaScript
  4. …Dev world. But this is surprisingly easy to achieve without frameworks, see [1] and [2] [1]: https://github.com/wilsonpage/fastdom [2]: https://youtu.be/sFMpS2_GqQc
    comment by writepub · 2019-05-19 · in Virtual DOM is pure overhead (2018)
  5. …logic is implemented in an AOT compiled language, it probably is much faster than a js v-dom [1]: https://github.com/wilsonpage/fastdom
    comment by writepub · 2019-04-22 · in Svelte 3: Rethinking Reactivity
  6. …said that, is a V-DOM required in 2019, if DOM updates are optimally batched, like in FastDom ( https://github.com/wilsonpage/fastdom ). Decades of optimizing browser internals would surely account for not trashing the DOM, if updated…
  7. …value proposition is questionable when DOM updates are properly batched ( like when using https://github.com/wilsonpage/fastdom ). Complexity is bound to increase with features, either in the back-end or front. But SPAs (with PWAs) offer…
    comment by writepub · 2019-03-11 · in A Front End Does Not Have to Be Rich
  8. …, a list of triggers at https://gist.github.com/paulirish/5d52fb081b3570c81e3a , and https://github.com/wilsonpage/fastdom for a common technique to avoid it by manually ordering read operations before writes.
  9. …batches read and write operations into separate queues and runs them using requestAnimationFrame: https://github.com/wilsonpage/fastdom
    comment by acdha · 2016-05-26 · in Faster DOM
  10. I think this is what https://github.com/wilsonpage/fastdom was designed to help with... The issue I have with it is it's another library to load...
    comment by taf2 · 2015-10-07 · in A Guide to Fast Page Loads
  11. …normal React practice. 2. See e.g. http://wilsonpage.co.uk/preventing-layout-thrashing/ 3. https://github.com/wilsonpage/fastdom
    comment by acdha · 2015-07-03 · in React Performance
  12. Or use fastdom[1], which batches reads and writes to reduce layout thrashing. [1]: https://github.com/wilsonpage/fastdom
    comment by yblu · 2015-01-29 · in Netflix Likes React
  13. To prevent layout thrashing yourself, you can use this library: https://github.com/wilsonpage/fastdom Ember.JS (and possibly Angular?) does this for you automatically.
  14. Well-researched feature. The best part of the fastdom wrapper ( https://github.com/wilsonpage/fastdom ) is that a timeout stub is introduced even for browsers that don't support native animation frames. Good job.
    comment by solox3 · 2013-10-05 · in Preventing 'layout thrashing'