Pretty sure the scary warnings in big bold text are more recent than this report.
Giving Saudi Arabia the 2034 World Cup has been a longtime coming. The 2030 World Cup was split across South America, Africa and Europe, yes really, under the banner of it being the ‘centennial cup’. Of course they could have held it all in South America, Uruguay being the original hosts.
In World Cup rules once a continent has hosted the World Cup they can’t hold it again for a certain period. So FIFA decided to hold it in three continents at the same time, thus reducing the available opportunities for 2034 and pretty much guaranteeing Saudi for 2034
A great video on this subject. https://youtu.be/q6h-a4GfYy4?si=npwu5xXxWScuPu1J
The show has real Late Late Breakfast Show vibes. An 80’s BBC show where the public took part in more and more over the top stunts. In the end someone died and the show was cancelled 3 days later.
https://www.everything80spodcast.com/the-late-late-breakfast-show-tragedy-of-1986/
The thing with serverless is you’re paying for iowait. In a regular server, like an EC2 or Fargate instance, when one thread is waiting for a reply from a disk or network operation the server can do something else. With serverless you only have one thread so you’re paying for this time even though it’s not actually using any CPU.
While you’re paying for that time you can bet that CPU thread is busy servicing some other customer and also charging them.
I like serverless for it’s general reliability, it’s one less thing to worry about, and it is cheap when you start out thanks to generous free tiers, at scale it’s a more complex answer as whether it is good value or not.
Amazon charges per hour for renting a server. Some are very expensive. It’s a common mistake to forget to turn off a server after you’ve finished using it and end up paying more than you planned.