Top all-time · #7205
Wilson Page
Personal blog · wilsonpage.co.ukwebprogramming
Wilson Page's personal blog at wilsonpage.co.uk covers web and programming. Since 2013, 11 different Hacker News readers have linked it 11 times, most often “Preventing 'layout thrashing'”. No feed was found, so read it on the site itself.
Too few sampled comments (6) to say how often HN recommends it.?
Why HN links it
Front-end development posts by Wilson Page, cited for DOM performance and avoiding layout thrashing, plus a Firefox OS install guide and a Grid Style Sheets CSS page.
Summarised by Claude from a sample of 6 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Preventing 'layout thrashing'5 people · 5 mentions · first linked 2013-10-05
- Onboard Mozilla Turbulence2 people · 2 mentions · first linked 2017-02-03
What Hacker News says?
The page isn't showing up in IE10 for me and is sluggish performance wise on Webkit (OS X and Windows). You can see the layout stutter when recalculating whereas with natural properties, layout recalculation is smooth. In Chrome, the layout barely reaches 30fps. Using CSS grids or flexbox would be more appropriate, and there is an outright lie on their section of flexbox. Flex items can be relatively sized according…
Comment linking /preventing-layout-thrashing/
on “Grid Style Sheets – CSS polyfills from the future”Submitted Preventing 'layout thrashing' as a story · 175 points
HN discussionIt's not just simple appendChild calls. I actually worked on an app which updated a large table – displaying file metadata, checksums calculated in web workers, etc. for a delivery – and found React to be around 40+ times slower than using the DOM[1] or even simply using innerHTML, getting worse as the number of records increased. The main trap you're falling prey to is the magical thinking which is sadly prevalent…
Comment linking /preventing-layout-thrashing/
on “React Performance”Submitted Onboard Mozilla Turbulence as a story · 2 points
HN discussion> could the DOM be pushed onto the gpu layer Some of it already is. The actual drawing-to-an-image happens on the GPU, so maybe that was a bit of a misnomer for me to point out in my last comment, but that's not the expensive part. Reflow is the browser deciding "here's everything on the page, here's all their CSS styles, and this one CSS style changed, or this new element got added, how does that affect everything…
Comment linking /preventing-layout-thrashing/
on “Unreal Engine 5 is meant to ridicule web developers”Submitted Onboard Mozilla Turbulence as a story · 2 points
HN discussion> ...with the only big advantage jQuery has now is if you're animating. While you can probably get away with using $.animate for very simple animations, you'll run into jQuery's animation performance problems before too long. See: - http://wilsonpage.co.uk/preventing-layout-thrashing/ - http://velocityjs.org/
Comment linking /preventing-layout-thrashing/
on “Stepping Backwards from AngularJS to JQuery – An Experiment”Submitted Introducing 'layout boundaries' as a story · 1 points
HN discussionIt is starting to takeover my mind too. My next app will be definitely in html5. There are many good articles and videos explaining how to manipulate the DOM efficiently (which is the main bottleneck of web apps I think). http://wilsonpage.co.uk/preventing-layout-thrashing/
Comment linking /preventing-layout-thrashing/
on “The State of HTML5 Development in the Enterprise”Submitted Batching image insertion as a story · 1 points
HN discussionSome very simple instructions: http://wilsonpage.co.uk/installing-firefoxos-nexus4/
Comment linking /installing-firefoxos-nexus4/
on “Firefox OS 1.5 on the Nexus 4”