← Back to context

Comment by nirui

1 day ago

Based on the setting `network.http.response.timeout`, which is timeout related, I'm *guessing* Firefox cannot distinguish between a network EOF or a logical/request-level EOF?

But that aside, it's kinda typical for a software from the developed world to have fault tolerance this bad. The engineer who wrote the code probably never ever annoyed by network error aside from a few well-known cases, and thus don't take these problems to their hearts.

For example, have you tried to download big files with a connection that has 100ms ~ 20seconds latency jitter? That happens with crossborder connections in/out of China. And in India, your users sometime experiences power issue which set their router to reboot or redial, that also causes an interruption in download.

Of course, people in these countries can't pay you much. But, these problems can all be solved/mitigated in software. Do you want to improve your software so it can be more robust, or do you want to waste user's time sitting in front your software just to get things done?

I think it's generally true that nobody really does good testing on machines that aren't top-of-spec and on internet connections that are at least 200MBps via a mesh network of some kind. There's an entire subaltern world of users who experience the worst of UI bloat and incessant network traffic of high-surveillance analytics capture tech (eg Fullstory, Microsoft Clarity) on very meager hardware with not-great internet connections.

Even in the Global North, rural internet is totally shit with no real fiber extensions out. Tech companies imagine a world where their users all uniformly have M5 Pros at minimum with 32GB of RAM (minimum - my last company gave us 128GB as default lol) and gigabit internet - it was always a joke when I would limit network activity and resource usage to emulate worse hardware when testing. That just gets in the way of deadlines and, plus, the poor can't pay for the service so why develop for them?

> That happens with crossborder connections in/out of China. And in India,

And sometimes in Germany. Let's not hail China again. /s

  • Stop using Deutsche Telekom and this problem will go away. They habitually avoid short routes because they are trying to extort all the recipients of traffic to pay thousands of euros per week for a direct connection. They only recently connected to Cloudflare, and they didn't publicize which side is paying, nor how much, but I hope it means DT is finally bleeding so many customers they're desperate.