Because half the world revolves around C fundamentals, sadly enough. Things would be a lot better if there existed a non-C portable way to share libraries across language boundaries (including libC).
Isn't the best way to solve the back button question to not be so damned complicated and just make certain that only things which you want to go back to ends up in the history? The whole framing of the problem just screams "structure your thing better and it won't be a problem to solve".
What? In this case the problem isn't that EU wants to dictate things globally, but US laws that do just that. EU laws just apply to Europe. As time goes on and European agencies get their shit together and actually start to follow their own rules, it will mean a shitton of business will leave US companies.
That "minor" detail seems to have been outside of all popular reporting I've read on the subject, any links to how large a part the EU would've contributed?
It was in the news (at the very least DN) a couple of months after the current government scrapped the plans for high speed trains. So Dec-Jan 22/23 or so. Googling for it to find the details have proven to be hard, so I can't say for sure if those articles referred to grants part of the CEF program, but very probably so. And I also obviously can't give any numbers without refinding those articles. But it was a fairly large share, based on memory.
EDIT: Found it! https://www.dn.se/ekonomi/regeringen-bad-eu-andra-tagkartor-... mentions it and that the possible numbers were really high, upwards 100GSEK or more. But only 'possible' numbers and not granted ones, so who knows how much it would have been in practice.
Getting to 200 was mostly a matter of upgrading tracks that needed maintenance anyhow in the 90s, in the 90s however cargo traffic wasn't causing as many disruptions and congestion as today and the talks about "new exclusive" lines is mainly meant to shift air-traffic to faster AND non-congested lines, but new lines are far more expensive/prohibitive both due to new land requirements and making it a "big-bang" build.
It makes sense in certain contexts, but it is batshit insane that it is enabled on a program (including any linked stuff) level. It would have made sense as numbers with separate types or perhaps even if you marked a region in code and it applied only to code in that region. Then the consequences of enabling it could be understood in ways that could be safe and usable (eg enabling it for a hot loop where the numerical ranges are well defined and safe in context).
reply