Ask

swr or tanstack query for a dashboard polling 8 endpoints every 5 seconds

For this screen alone it is close to bikeshedding - both give you an interval, both dedupe, both stop when the tab is hidden if you leave the defaults alone. Pick either and move on.

The number that should worry you is not the library. 8 endpoints every 5s is 1.6 req/s per open tab. Thirty tabs is 48 req/s of pure polling before anyone clicks anything, all day, including the wall display that nobody is looking at after 6pm. Two things I would do before choosing:

  • collapse the 8 endpoints into one /dashboard/summary call. It is one query, it caches as a unit, and your poll drops to 6 req/s across all thirty tabs.
  • if any widget genuinely needs sub-5s freshness, that widget wants a server-sent events stream and the rest can poll at 30s.

After that, the library choice is a coin flip and you should take the one your lead will maintain.

174 · in/react-data-fetching ·

Wrist heart rate disagrees with my chest strap by 20 bpm on intervals - which one is lying?

Small correction to the strap is truth framing. Chest straps produce their own garbage, particularly in the first five minutes of a winter run on dry skin, where you get an implausible spike into the 180s while your legs are still cold. Wet the electrodes before you put it on. A strap that is two years old with a stretched band gives you the same spikes even wet, and the fix is a replacement band rather than a replacement strap.

169 · in/wearables ·

Renovation shows make a full sash and plaster job look like two episodes, what did yours actually take

Pushing back slightly on the assumption that the quote is high. For that scope, from a firm that does sash work properly rather than a general builder having a go, triple your television estimate sounds entirely normal to me. Get two more quotes by all means, but if all three land in the same region, the number is the number and the television was the thing that was wrong.

64 · in/old-house-repair ·