3 ms·
I’ve opened facebook.com with browser dev.tools open. The 3 largest java script files are using 1 megabyte to download. Facebook is able to do that because even
by Const-me 5y ago
I’ve opened facebook.com with browser dev.tools open. The 3 largest java script files are using 1 megabyte to download. Facebook is able to do that because even globally, vast majority of people have internet way faster than 64 kbit/sec. 1 megabyte takes more than 2 minutes to download at 64 kbit/sec.
It’s similar story with CPUs. Modern CPUs are insanely fast these days, smart phones included. What once required purposedly-designed ASICs (e.g. Sony Minidisk had one for ATRAC3) is now borderline free in terms of compute power. A cheap Android phone sold 10 years ago gonna have at least 500MHz CPU, and at least 256MB RAM.
96 Kbps AAC audio works on 10-15MHz CPUs, and 64 Kbps HE-AAC works on 50-60 MHz CPUs, both from 2005: https://www.helixcommunity.org/projects/datatype/2005/aacfixptdec https://www.helixcommunity.org/projects/datatype/2005/aacfix...
- miki123211 5y agoThere's much more to an internet connection than the average speed per second. If we're talking about downloading files (and loading websites), you're mostly correct. However, temporary slowdowns, disruptions in wireless connectivity and wireless-specific packet loss affect audio quality a lot, while not having much impact on your download speed. Even when streaming audio or video, you don't feel them as much, as your device usually keeps at least 10 seconds of buffer that it can rely on. When in a call, though, 10 seconds of buffer would mean 10 seconds of latency, which is simply unacceptable. You can have a 1.2 mb/s connection that sometimes goes down to 64kb/s for two to three seconds. Even if your download speed is still 1 mb/s, you can't really receive more than 64 kb/s when in a call, or you will get dropouts.