If you have a month pass it frequently forgets at the end of the month, and you have to repeatedly look it up. When you look a ticket, it doesn't remember it in the app, so you have to look it up again for your return trip.
It also periodically forgets all of your tickets locally and needs to resync from the network. It doesn't matter if you were just looking at the ticket three minutes ago. This ie especially annoying if your train is underground after leaving the station, and they are collecting tickets while you have no Internet access.
I don't know. Last year I was trying to buy bullet train tickets for an upcoming trip to Japan, only to find that the booking website operated only during daytime work hours (Japanese, of course). Then there was me trying to buy train tickets from Mt Fuji area to Tokyo. I could buy them, but they could only be picked up in Tokyo, not Mt Fuji! That was a pretty major wtf, given Tokyo was our final destination.
Not because I doubt you but Europe is pretty disparate.
Amtrak from NYC to Philadelphia cost as much as a flight to continental Europe, and the experience was abysmal, truly awful I couldn’t even get the tickets for hours and took a bus instead.
Perhaps I’m “spoiled” by UK and Swedish trains but UK is pretty terible
It depends hugely on when you book--both time in advance and time of year--as well as any sales going on. Which can vary a TON in Europe as well. I almost always take trains within Europe but they're no bargain.
Right. I'm not going to NYC for now but I saw the end-of-year sale in my inbox recently. Pricing varies a lot. (And I usually don't book Acela on my own dime absent a bargain; the transit time isn't much different from the regional.)
I've been wanting them to have an api for years with a TOS that you cannot resell tickets or make any additional fees from the sale to discourage SEO snakes from hijacking things.
A more reasonable front-end could be made without much effort and a very low monthly overhead to host since it's mostly a proxy
Require the same upsells with the insurance and credit card offer I don't care, that's not the problem I have with the site.
API only access where a frontend is currently available should be a legal requirement. For one thing, not doing so is prejudicial regarding accessibility.
I really yearn for a world where we stop making people deal with all these garbage frontends. Especially in the coming age of personal LLMs on device - anyone should be able to create their own frontend for any service and drive their own version specifically tuned to them. Make the standard frontend as simple and accessible as possible (minimal scripting - I think you could have a government agency set this as a regulatory limit in terms of KB of JavaScript) and just cut the fat and the abhorrent waste.
Clients will ship with defaults. Most people's personal tunes will not deviate much from each other at all. But people who actually care can make it as interesting as they want. Instead what we have now is a system that incentivizes people to make the default too interesting to justify their own employment. It's rare to come across a frontend these days that doesn't scream absolute garbage.
At one place I worked, the two releases that made us the most nervous went out on Friday the 13th, and Halloween (IIRC). The reasons that they made us nervous had nothing to do with the release dates. We were nervous that what we did had hidden bugs, and even after testing, we were still somewhat nervous.
Now that US AI psychoses is reaching pandemic levels, I wonder if governments outside the US will accelerate their migration plans. Too bad we can't socially distance ourselves, wash hands and wear masks.
When I get back to the office on Monday I'm going to start making steps to make sure that skill atrophy gets limited so that we don't fall into the same helpless incompetence.
If you have a month pass it frequently forgets at the end of the month, and you have to repeatedly look it up. When you look a ticket, it doesn't remember it in the app, so you have to look it up again for your return trip.
It also periodically forgets all of your tickets locally and needs to resync from the network. It doesn't matter if you were just looking at the ticket three minutes ago. This ie especially annoying if your train is underground after leaving the station, and they are collecting tickets while you have no Internet access.
Not because I doubt you but Europe is pretty disparate.
Amtrak from NYC to Philadelphia cost as much as a flight to continental Europe, and the experience was abysmal, truly awful I couldn’t even get the tickets for hours and took a bus instead.
Perhaps I’m “spoiled” by UK and Swedish trains but UK is pretty terible
If you book a train from NYC to Philadelphia on Dec 9, there are four trains leaving before 6am with coach tickets for $10.
NYC to Boston has similar early morning prices.
They acted like I was committing a crime at the service desk too tbh. I’m not sure how they are in business.
Sorry, as an American Amtrack’s website isn’t even in my top 5 of worst train websites.
Fair point about refunds for delays in general, its so awful I normally don’t do it. Not with trains, busses nor airlines.
A more reasonable front-end could be made without much effort and a very low monthly overhead to host since it's mostly a proxy
Require the same upsells with the insurance and credit card offer I don't care, that's not the problem I have with the site.
API only access where a frontend is currently available should be a legal requirement. For one thing, not doing so is prejudicial regarding accessibility.
I really yearn for a world where we stop making people deal with all these garbage frontends. Especially in the coming age of personal LLMs on device - anyone should be able to create their own frontend for any service and drive their own version specifically tuned to them. Make the standard frontend as simple and accessible as possible (minimal scripting - I think you could have a government agency set this as a regulatory limit in terms of KB of JavaScript) and just cut the fat and the abhorrent waste.
Clients will ship with defaults. Most people's personal tunes will not deviate much from each other at all. But people who actually care can make it as interesting as they want. Instead what we have now is a system that incentivizes people to make the default too interesting to justify their own employment. It's rare to come across a frontend these days that doesn't scream absolute garbage.
(1) https://en.wikipedia.org/wiki/Cascading_failure
Without planes, lots of them probably just tried to rush to Amtrak and they received a volume they’ve never seen in a very short order.
I doubt there is anything more complicated than that.
Both releases were clean. Go figure.
Coming soon: car rental sites, hotel booking sites, food delivery services, taxi and ride share services.
(context: https://news.ycombinator.com/item?id=50482379)
When I get back to the office on Monday I'm going to start making steps to make sure that skill atrophy gets limited so that we don't fall into the same helpless incompetence.
And is not connected to the internet.