News for hackers. Stuff that matters.
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by tomnipotent on Monday May 11, 2020 @01:50PM (#23144888)
Those metrics are useless in 2020, they do not capture perceived load to the user adequately.
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by lhorie on Monday May 11, 2020 @01:56PM (#23144953)
Every time I see metrics being dismissed in response to someone pointing out perceived bloat, I'd love to see what _other_ metrics they are using instead.
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by tomnipotent on Monday May 11, 2020 @01:58PM (#23144992)
Bloat != perceived load time.

The only thing I've found these metrics useful for are baselines for regressions over time.

Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by lhorie on Monday May 11, 2020 @02:16PM (#23145216)
"Perceived load time" is not a panacea, and not a substitute for actual metrics. Do you actually go interview users on what they perceive? If one doesn't, and is instead just looking at the code _they_ wrote and thinking "yeah my code feels fast", that's biased, unscientific, and objectively an inferior quality assessment strategy than just looking at TTFB/TTI/etc and deriving conclusions from those hard numbers.
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by tomnipotent on Monday May 11, 2020 @02:27PM (#23145351)
The only people I see obsess over these metrics have either their ego or pay tied to them.

> Do you actually go interview users on what they perceive?

Yes, regularly, because that's what effective teams do. I also limit bandwidth to 3G and record the sessions so that everyone can share in the learnings, which very rarely circle back to things like TTFB/TTI.

Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by lhorie on Monday May 11, 2020 @02:50PM (#23145581)
Interesting! How do you iterate / keep track of regressions?
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by tomnipotent on Wednesday May 13, 2020 @02:54PM (#23170336)
Speedcurve.com - download the data and then use basic outlier detection on the time series as well as individual observations looking for anything out of the ordinary. Most of the time it was marketing uploading a 20MB PNG to the CMS, other times it's some 3rd party JavaScript (looking at your Criteo) doing something questionable.
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by leeoniya on Monday May 11, 2020 @01:58PM (#23144989)
there is more to "load" than "perceived load".
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by tomnipotent on Monday May 11, 2020 @01:59PM (#23145002)
No, there isn't. Nothing is more important than perceived load, everything else is just filler.

Time to fist byte? Last byte? First paint? Interactive? These are great, but do not always capture the entire picture of what's actually important - do your users perceive the experience as fast?

Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by leeoniya on Monday May 11, 2020 @02:00PM (#23145026)
what i'm showing is objectively better in both perceived load and actual/real load. so i'm not sure what your argument is.
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by tomnipotent on Monday May 11, 2020 @02:14PM (#23145189)
Just because a Ferrari is faster than a Corvette, does not make the Corvette slow.
Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by leeoniya on Monday May 11, 2020 @02:17PM (#23145231)
> Just because a Ferrari is faster than a Corvette

to quote Rick & Morty: "Must be nice!"

Re:Next.js 9.4 – Fast Refresh, Incremental Static Regeneration by tomnipotent on Monday May 11, 2020 @02:22PM (#23145291)
ThermoTile is really fast - like 2001 site on 2020 bandwidth fast. Great work.