Categories: Technology

Jeff Bezos is not allowed to sail under the historic bridge in Rotterdam. The bridge will be dismantled

The De Hef Bridge in Rotterdam is definitely a historic building. Moreover, it is liked by the inhabitants of this city, who once defended it against demolition in the 1990s. Now they will not defend it. Fortunately, the bridge will only be gone for a few weeks.

The whole culprit behind the Dutch bridge confusion is Jeff Bezos and his Y721, the ultra-modern and of course the world’s largest yacht, which cost 430 million euros and was built at the Alblasserdam shipyard, near Rotterdam. And once its construction has been completed, you can start sailing it on the sea. For this to happen, however, Y721 has to reach the sea, and unfortunately it turns out that the only possible route for this unit is through the Koningshaven harbor basin in Rotterdam and under the De Hef bridge, under which it will not squeeze.

So Jeff Bezos will pay for its demolition and reassembly

The media cites this news as shocking, which makes me shocked, because it’s not that the problem appeared suddenly and no one was prepared for it. It is of course quite the opposite. The Rotterdam authorities are quite well prepared for the whole situation, ie everything has been planned. The bridge will be dismantled and reassembled by specialists, Jeff Bezos will pay for the entire operation, so the inhabitants of Rotterdam will not be charged with any costs and… well, that’s it.

Advertising

Neither is De Hef a key transportation hub. Yes, it used to be a very important railway bridge, but now its main role is to be a very nice monument (if one likes bridges) that has been taken out of service. The only objections to the entire operation are raised by the Rotterdam Historical Society, whose representatives, quite rightly, fear that the elements of the bridge will be damaged during the demolition and reassembly.

Also read: Jeff Bezos broke a wealth record

After De Hof was fully restored a few years ago, these concerns are completely understandable. The Mayor of Rotterdam, in turn, emphasizes that the construction of the Y271 has created new jobs for Rotterdam residents, so the city feels obliged to provide the mega-yacht with the only route leading to the sea.

And that’s about it. Demolition and reassembly of the bridge will take place in the summer, a specific date has not yet been released to the public. The entire operation is to take several weeks and if its course is as planned, no one will suffer from this situation.

Miners Hashrate

Recent Posts

Mining RTX 3070 at NiceHash: Overclocking, tuning, profitability, consumption

Mining on RTX 3070. Overclocking, tuning, profitability, consumption: If you are interested in finding more…

6 months ago

Mining GTX 1660, 1660 Ti, 1660 Super: Overclocking, settings, consumption

Mining with GTX 1660, 1660 Ti, 1660 Super. Overclocking, settings, consumption, profitability, comparisons - If…

6 months ago

Mining RTX 2070 and 2070 Super: Overclocking, profitability, consumption

Mining with RTX 2070 and 2070 Super. Overclocking, profitability, consumption, comparison What the RTX 2070…

6 months ago

Mining with RTX 3060, 3060 Ti. Limitations, overclocking, settings, consumption

Mining with RTX 3060, 3060 Ti. Limitations, overclocking, settings, consumption, profitability, comparison Let's look at…

6 months ago

Alphacool Eisblock Aurora Acryl GPX-A Sapphire – test: 2.8 GHz++ are not an issue

Alphacool Eisblock Aurora Acryl GPX-A (2022) with Sapphire Radeon RX 6950 XT Nitro+ Pure in…

6 months ago

Corporate Crypto Strategies 4.0: Leading with Bitcoin Expertise

In the ever-evolving landscape of business strategy, Bitcoin has emerged as a pivotal asset. With…

6 months ago

This website uses cookies.


Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420

Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420