this post was submitted on 27 Aug 2026
318 points (98.2% liked)

memes

22489 readers
2335 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/Ads/AI SlopNo advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.

A collection of some classic Lemmy memes for your enjoyment

Sister communities

founded 3 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] FooBarrington@lemmy.world 1 points 1 day ago* (last edited 1 day ago)

I'm not sure I agree. The real world is never going to run perfectly, so some slack must be included (either by adding buffer time to schedules, or using the way you mention). Of course there are examples like Japan that have done a really good job at optimizing these systems, but you won't be able to successfully apply their approach to every country. Some locations require more work to achieve this, others require less.

Generally the closer you get to an "ideal" performance, the more costly every further improvement gets. If 7 min isn't reasonable, what number would be? Say we manage to shave off two minutes, at twice the cost of the current system. Is that really worth it?

The better approach is to include reasonable slack time in people's train schedules, while increasing frequencies so missing a connection doesn't result in hour-long wait times.