[HN Gopher] Blocking=render: Why would you do that?
___________________________________________________________________
Blocking=render: Why would you do that?
Author : pinjasaur
Score : 31 points
Date : 2024-08-14 20:47 UTC (4 days ago)
(HTM) web link (csswizardry.com)
(TXT) w3m dump (csswizardry.com)
| CM30 wrote:
| The A/B testing use case is probably the one good one there, at
| least if you can't serve the variations on the server side. So
| many issues come from trying to overwrite the page without it
| flickering/being blatantly obvious to the user.
| csswizardry wrote:
| Honestly, I should add the point that client-side A/B testing
| is the devil and should be avoided in the first place.
| wizzwizz4 wrote:
| But sorting all the paragraphs in alphabetical order
| increased reader engagement metrics! How would I ever have
| discovered readers wanted _that_ without A /B testing?
| CM30 wrote:
| Ideally it should be on the server side, so you're right
| there. Client side A/B testing isn't the best way to handle
| things.
|
| However, it's sometimes a necessary evil due to:
|
| 1. The original company not budgeting time/effort from their
| existing dev teams to work on A/B testing, and wanting to
| outsource it instead.
|
| 2. Said company and their tech department being nervous about
| letting outsiders actually access the source code for their
| site/app.
|
| 3. Or said company wanting the analytics/features that
| VWO/Target/Optimisely/whatever offer, and not wanting to have
| code up the same analytics toolbox themself.
| thanatos519 wrote:
| Could this be used to prevent me from clicking on or tapping the
| wrong thing because new items keep appearing causing a reflow
| just as I jab? I would really appreciate it if pages would render
| _after_ they have made up their mind.
___________________________________________________________________
(page generated 2024-08-18 23:01 UTC)