4 ms·
Unfortunately this isn't the perfect solution as there is no universal device or average user. Especially with music, mixing songs for earbud/headphones will pr
by qqii 7y ago
Unfortunately this isn't the perfect solution as there is no universal device or average user. Especially with music, mixing songs for earbud/headphones will produce a worse quality song for another pair. In the same way we've seen software written by users primarily using x86 work less effectively when compiled to arm. Plenty of open source projects are developed on by people with less than adequate hardware yet they're still bloated and slow.
I think it's very sensible (if a little unrealistic) to test applications on as many pieces of intended hardware as possible, and this somewhat reminds me about this story of snow clearance[0], where the solution was not only the intrudction of a new perspective but also empirical measurements.
[0]: http://info.gritit.com/blog/what-is-gender-balanced-snow-clearance http://info.gritit.com/blog/what-is-gender-balanced-snow-cle...
- hnuser123456 7y agoNo one said you have to test on everything. Just adjust your target and testing hardware to something midrange, maybe even budget optioned. As above, test on some mid-range or even budget-level 2015 hardware, laptop or phone, and if it's smooth on that, it'll be smooth for people running 2020 hardware. You can never be sure about the reverse. That being said, there's a lot of crap software out there that's slow even on 2020 hardware.