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.
See also https://sh.itjust.works/u/p1mrx
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.
if we all started counting in base12 too
You could start by calling it twelve instead of 12.
So 1/2 ft, 1/3 ft, 1/4ft and 1/6 ft all have a whole number of inches
The same is true if you start with 300 mm instead of 1 foot.
Though dozenal numbers with a corresponding dozenal metric system would be very convenient, if you ignore the enormous cost of switching.
“The future is already here – it’s just not evenly distributed.”
You are 10% hydrogen already.
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.
Between 2017 and today, it was a mostly-blank page with the letter “x”: https://web.archive.org/web/20230722020649/http://x.com/
BL-5C is becoming a de facto standard size for random electronics, but it’s too small for a smartphone.
It’s more like 3 really wide pixels.