7 ms·
> Also, this turns out to be an actual bottleneck way more often than people notice. I wish more devs -- particularly web front-end devs -- tried out their wor
by nirvdrum 7y ago
> Also, this turns out to be an actual bottleneck way more often than people notice.
I wish more devs -- particularly web front-end devs -- tried out their work on something that isn't a top-of-the line developer computer. There are plenty of devices out there that are computationally constrained and/or memory-bounded. Moreover, no one ever runs these things in isolation. So, while profiling in isolation makes a ton of sense to rule out external factors, in the real world you're competing with all the other open tabs and windows. That's a tricky problem to model, of course, but it doesn't mean we shouldn't try.
- d0m 7y agodeploying the same javascript code on both web and old android devices (using RN) keeps you honest about performance :O
- tomxor 7y ago> I wish more devs -- particularly web front-end devs -- tried out their work on something that isn't a top-of-the line developer computer. I agree, and I am, and I do. I held out on laptop from 2009 until recently, it had a core 2 duo, It was (and is) a really good machine for showing up sloppy performance hungry websites, and has been the source of a few of my rants here on HN when discovering some stupid side JS animation saturating one of it's cores unnecessarily. I agree there's a lot of shitty JS code out there. But there are a few of us web devs that care, and will do anything we can to prevent the crap we see around us.
- pault 7y agoIt's best to test on an actual device, but chrome developer tools does have CPU and network throttling to simulate slower machines.