@robryk Heh, at least a tram is going at less speed.
In my case it looks like we're taking a very odd path (I wouldn't expect a train from Erfurt to Frankfurt to go through Bamberg). I'm guessing in yours GPS might just have been wrong. :>
✅ Signs telling me what seats are reserved
✅ Luggage racks designed to actually be useable
✅ 13 carriage train that needs a dwell time of just 1 minute in major stations
✅ Staff providing useful information about connecting services
✅ No superfluous announcements about forgetting luggage or minding the doors
✅ Freight trains too!
@jon I saw your complaint about the large dwell times and yet it feels like you can run your network more reliably that way. I mean at this point I consider DB's departure times as aspirational. Of course your example with SNCF was pretty extreme. At least with local trains in CH I also saw some slack in the system and now I wonder if that'd actually help...
Want to book a Interrail seat reservation for a TGV, TGV Lyria or Eurostar?
Don't bother using anything other than Rail Europe any more. Don't mess with ticket machines. Avoid extra booking fees. Just use Rail Europe. That's it.
@jon Could it be that Interrail fixes some of the problems of getting to the Eurostar (e.g. missed connection) and its price then? What's the order of magnitude of prices for the reservations here?
Sind technische Studiengänge in Deutschland eigentlich immer noch so schlimm? Ich bin damals raus, weil wir code auf Paper runter schreiben sollten, man hart und ohne Witz auf deutschen Fachbegriffen bestand (Keller, Halde, Hafen), und mir classfull routing als Lösung für richtige Dimensionierung von Netzblöcken (vom Leiter des lokalen Fraunhofer-Instituts, der eine der Basis-Vorlesungen hielt) präsentiert wurde. Ausserdem waren die Komilitonen arg hässig. Das war mir dann irgendwann zu dumm.
@fink@nblr@LangerJan Halde und Stapel sind schon noch Begriffe, die man mal sieht, insbesondere wenn die Fakultät schon älter ist. Hafen ist mir aber nie über den Weg gelaufen.
@nblr@Zugschlus The return path, as nibbler already wrote, is always calculated at the point of reply. So if you hit a router in FRA again it is almost certain that it has a cheaper route locally than across the pond. That's where the reply packet is generated.
@Zugschlus@nblr If the preferred cross connect from Cogent to DTAG is in the US, why is it implausible? That's exactly what I'd expect. Go across the pond twice, aka 80ms.
@nblr@Zugschlus I wasn't making fun, either. One interpretation here I could see is "why does 62.157.249.201 use the ~same physical path length to FRA as the JFK router from Cogent instead of its own". But we don't know what path the other JFK routers take back, but it might be just the same DTAG link the route is already showing. (We don't know where the trace is starting and ending.) The 80ms already includes the way back, after all.
