> they weren't stupid technically, just stupid from a business sense
I wouldn’t call them “stupid technically”, but assuming that there was a hard limit to codec efficiency and to internet bandwidth would at least make them technically naive in my opinion.
The prospects of building something new with this tech are very distant. Just to get an approval for construction in Germany it can take years and then there will be traditional delays along the way. We won’t see it in any meaningful quantities before 2030-2040 - whether this project will survive until then is an open question.
The acute service problem on the other side could be addressed by simpler means like investment in IT and better internal processes. My last trip was cancelled one hour in advance, despite that they knew it couldn’t happen days before. I had to visit their travel center, because the app couldn’t apply my seat reservation to alternative route, and that experience was awful. It is very hard to understand why some tech that may never see the light due to bureaucratic hurdles deserves investment at the time where service doesn’t show any signs of improvement.
I mean, you can ask the meteorologists about the process of naming, but those hurricanes actually existed, on the dates suggested, so I'm not sure what's "fishy" about it.
I believe that the naming relates to which ocean they're forming in, but it's probably good for you to do your own research, so you can clear up any "fishiness" yourself.
I can’t help but mildly cringe when I read sentences like “the X that shouldn’t exist”, for example when applied to the Antikythera mechanism. It’s a weird way to mask our ignorance about the item being discussed.