Waste management is similar to handling forever toxic chemicals waste- bury deep underground. Check out what herfa-neurode facility is.
It's not the most expensive form. Some current builds are expensive, but it generally can provide for very cheap. Check out Goesgen open data for Switzerland
In Germany, the search for an underground facility is ongoing.
They hope to find a facility somewhere in 2046 [0]
In 2024, the cost for storing nuclear waste just up until 2100 was estimated to be 170 Bln. [1]
This cost is always, without exception, excluded in the calculation of the cost of generating a MWh. It's externalized, paid for by the next generations of taxpayers.
Gösgen's open data, just like all the other data, does not include waste management cost.
Gösgen is a perfect example for how brittle and outdated the technology is. The nuclear plant is off the grid since May 2025 and will remain down until at least February 2026 [2]
Just like the newly-built Flamanville 3 (12 years late, 10+Bln over budget), it's off the grid until further notice. [3]
1- no, it's not ongoing but stalled. Last year almost a billion was spent for searching. Can you pinpoint where the money went?
2- It's covered by kenfo, auto reinvested fund paid by operators. It has about 24bn. In comparison Onkalo in Finland did cost 1bn to build. A similar repository is built in Sweden in Fosmark
3- Goesgen data does include the tax for both waste handling and decommissioning, didn't you read the data?
4- you don't seem to understand why Goesgen is offline. It's not about being brittle. They installed new equipment that performed too good and they need to upgrade other connected components
5- Flamanville did cost merely ~a single year of German EEG subsidies for renewables
6- 2024 was record TWh from nuclear, for like, ever. It'll grow more, mostly due to Asia unless Hitachi/Whous/EDF will do something
Today, the vast majority of commercial PHP projects are developed enforcing the use of strong types by static analyzers like PHPStan in the CI pipeline, and having the strict_types declaration set.
As a community, we've seen enough untyped PHP spaghetti code in the early 2000s and never want to go back there.
If your team prefers not to use this new optional feature, just enable a PHPStan rule in your CI/CD pipeline that prevents code like this getting merged.
OkCupid (the original one, before they sold out) had a great article showing how your perceived attractiveness changes significantly, based on the camera you're using to take your profile pictures [1]
If you're bookmarking a directory, a list of things (e.g. the HN frontpage), you expect the content to change when opening the bookmark.
You bookmark a link to the directory so you don't forget the directory's entry URL.
The use case the author is talking about is a different one: You are configuring a complex item in a shop, and want to bookmark the URL so you can save it, recall it later, share this configuration with someone, or compare it with a different URL.
In this case, you also would expect little details to change (pricing, descriptions, photos) but the structure of the state should stay the same.
It's very frustrating when you share a link to a product detail page, only to discover that all your filters and configurations have been lost.
Also, this is very regional.
Here in Europe, actual, big projects that need to make money use Symfony, not Laravel.
reply