I haven’t had the courage to run executable code from P2P networks since the early 2000s. Even then it was probably a bad idea.

chrome : chromium :: vscode : vscodium

That’s a good pun. Clearly the authors have mastered the second hardest problem in computer science.

Google is at fault here for creating the software-defined garbage, but they’re not literally selling the products, are they?

AOL came on floppies originally, but the quality was so poor that you could barely rewrite them.

I’m made of meat.

Well, if you currently have this problem and want to fix it, I’ve shown you the way. OpenWrt is free software.

Otherwise, there’s no point arguing about it.

Multi-hour downloads have been a thing since capacity was measured in kbps. If a simple TCP transfer causes excessive queueing, then the queueing algorithm is broken.

A router with OpenWrt and luci-app-sqm can fix this problem, at least for an internet connection with a fixed speed limit.

One major AAA game update will likely break your connection
One person in the house uploading anything will cripple your ability to make ANY request

You are describing symptoms of bufferbloat, not capacity problems.

Android still doesn’t support DHCPv6 and will be left without a valid address.

RFC 7934 explains their reasoning, though it’s not exactly an ironclad argument.