| ▲ | sillysaurusx 5 hours ago |
| If you’re interested in this kind of thing, look up plainly difficult on youtube. He has more videos on train crashes than I’ve seen, and I’m embarrassed how many I’ve seen. Here’s one to get you started: https://youtu.be/VV2rIHEp5AM?si=sSBT9s49PqbLTGbt There are a lot of safety lessons embedded in these videos, which is why I like them. I also did a double take when I heard "semaphore"; its history goes back far longer than the ~century of software engineering. https://en.wikipedia.org/wiki/Semaphore |
|
| ▲ | bigmeme 4 hours ago | parent | next [-] |
| Oh you silly duck! Semafor is a common word in a handful of other languages for things like traffic lights and such. I had to do a double take when I first saw it in a programming class. Also hope you’re doing well it’s been a minute since our paths crossed on gdnet. |
| |
| ▲ | rob74 2 hours ago | parent | next [-] | | "Semaphore" is (old) Greek and means "sign (sema) bearer (phore)", and actually the meaning in railways and computing is more or less the same: in computing, a semaphore signals if a resource is in use; in railways, the resource is a segment of a railway line, and the user is a train. | |
| ▲ | seanmcdirmid 2 hours ago | parent | prev [-] | | [flagged] | | |
| ▲ | karmakurtisaani 2 hours ago | parent [-] | | Copy pasting AI vomit is like leetspeak or all caps. Should not be used in online discussion. | | |
| ▲ | seanmcdirmid 2 hours ago | parent [-] | | I disagree, but we are all entitled to our own opinions, and I get that there are a lot of luddites on HN these days. The fact that you consider it vomit rather than useful information just says more about you than me. If there was just a wiki page on how railway terms were used in computing, I would have just linked that (search didn't turn up anything in the first few pages). | | |
| ▲ | orwin an hour ago | parent [-] | | At least ask it to summarise. I'm not against reading AI text, but the more verbose it gets, the worst reading it feels. | | |
|
|
|
|
|
| ▲ | delta_p_delta_x an hour ago | parent | prev | next [-] |
| The basics of mutual exclusion algorithms were developed for railway timetabling and track signalling. |
|
| ▲ | cyode 4 hours ago | parent | prev [-] |
| No cause is known yet, but based on the videos, what’s the most likely reason for crashes? Bad tracks? Some human error resulting in collision? |
| |
| ▲ | anonu an hour ago | parent | next [-] | | I don't want to speculate on this crash but my mental model for these things is that there's always a handful of factors that all align and converge to create an accident. Some factors are deep-rooted - and point to decisions made years ago - sometimes related to company culture. Theres always an element of operator error: someone ignored something due to inattention or sleepiness. | |
| ▲ | 2 hours ago | parent | prev | next [-] | | [deleted] | |
| ▲ | scoot 33 minutes ago | parent | prev [-] | | What's the befit of speculating at this point? Let the investigators investigate, and hopefully some lessons will be learned. |
|
