> They were aware there were issues, and negotiations happened on how to fix them, with the French leaving them with the impression everything is good.
The French culture is to never deliver bad news before the deadline has arrived. Underlings will never tell their boss that something is impossible, decisions will be made by grande-ecole-bosses without technical expertise and relationships are valued far higher than knowledge and expertise. You'll always get the first impression that all is well and they'll manage before the deadline. If you need a real non-sugar-coated insight as to how the project is going you need to gather your own data. Discreetly.
However, as soon as shit has hit the fan and bosses got involved, they'll bend over backwards to make things work. But you cannot expect meeting the first deadline, ever. Same for the first budget. Subsequent ones depend on the size of the project.
On the original contract in 2016, Germany also bid and in all likelihood could have won, since Germany has far more experience with building non-nuclear subs with Diesel or fuel-cell drives. France had to start the designs almost from scratch since they offered a redesign of their nuclear subs. France desperately wanted the contract and probably only won the bidding by intentionally bidding too low and too quick, downplaying their technical challenges. This behavior of France has bitten various European supposed allies and supposed good neighbors a number of times. Either they got outbid by a phony French bid. Or they were customers of such a bidding process, getting endless delays and price overruns.
So I'd be surprised if there were any substantial EU backing for France in this matter.
These things, like user accounts, more auth methods, flexible endpoints, IP pools, ..., should be integrated in a product in a secure manner. What wireguard does is the irresponsible lazy approach of leaving everything up to the VPN providers and webinterface-monkeys. Who will surely mess up a lot of the upper layers that provide all the necessary "comfort" features. After which the wireguard crowd will wash their hands with the Jobsian "you are holding it wrong".
There are, but they can only audit and report. Change and punishment would need to happen politically, but that would need a majority of states. Two thirds of the states profit from Laenderfinanzausgleich (to various degrees) and will not change anything.
Lowering rents was part of the plan anyways, I think. Market manipulation through rent caps has been tried before and (in the Berlin version) declared unconstitutional.
Context switching overhead is bad for microkernel performance. All the reasons why the userspace wireguard implementation was slower apply to each and every part of a microkernel system. And all of this got worse with spectre and meltdown, secure context switches are now even more expensive. Modern CPUs generally always increase the context switching cost, they optimize for single-process benchmarks.
So microkernels are dead, performance buries them deeper and deeper.
Problem is, "not be paying market rates" will never happen. Market rates will be paid, because disowning anyone for the public good is only constitutional, if market rates are paid as restitution. There have been lots and lots of cases around disowned people lost by the state because of that.
Berlin doesn't care about money. Back when separated by the iron curtain, Berlin always got a special deal in federal/state finances because of its situation. After reunification, Berlin was pumped full of money because it was the new designated capital city and showpiece for unification. Nowadays, some of the special deals still remain, plus Berlin is awarded absurd amounts of money from the "Länderfinanzausgleich" (state finance balancing mechanism), meaning that the richer German states pay for Berlin's deficit.
So Berlin is in the comfortable situation of that one no-good family member on social security who will always find someone to pay their bills. Why change anything, why stop spending all that money, if more keeps coming without any effort in any case?
Nope, UCS-2. Which is UTF-16, but just the BMP, so only the first 65k codepoints and all characters are fixed-length 16bits. Only later windows versions at some point learned UTF-16.
Well, easy in case of VW: If the optimization involves checking "steering wheel has never moved out of 0 position since engine start" and "intake air is at exactly 293K", then it illegally optimizes for a test.
Red tape. Medical devices need to (depending on type and country) conform to medical device regulations, be approved by a medical device regulator, be sold only to medical professionals or people with a script from a medical professional. Liability in case something goes wrong because of your device is expensive, adversarial and dependent on crossing all the 'i's and dotting all the 't's. There are "lower levels" of this due to regulations being less for more harmless devices. E.g. you can nowadays get thermometer, pulse-oximeter or a blood pressure meter quite cheaply. But anything just mimimally more complicated or critical gets expensive very fast.
Reasons for this beside the red tape are imho the low number of customers (most slightly specialized medical devices are needed once per patient with $rare_disease, once per lab or once per doctors office), the high need for customization (one-size-fits-all doesn't even work for blood pressure cuffs, let alone prosthetics), localization (broken i18n can kill, most customers are elderly and therefore not as versed in engrish), higher component cost (sterilizable plastics are more expensive, bigger displays for vision-impaired elderly clients are more expensive) and acceptance of foreign/small/unknown manufacturers (won't trust my elderly mother's health to a device from "Corty's Refurbished Asbestos Plates, Health Equipment and Luxuries Ltd., Templestreet, HongKong (CRAPHEALLTH)").
There is also a cartel of each medical professionals, manufacturers, insurance companies/public insurance pools and politicians, complete with revolving doors, kickbacks, fake or real -but always suspiciously convenient- scientific data, and exclusionary legal situations. All cementing the status quo and the wealth and standing of all participants (except the patients' of course).
Microsoft doesn't cater to the more knowledgeable admin population I guess. They are used to the point-and-click crowd mindlessly accepting every answer as gospel. Because usually you can't prove them wrong anyways, everything being opaque and closed in Microsoft-land. And because of that, MS/Windows admins never learned how to get to the very bottom of things.
Transmission or no transmission is a huge difference in maintenance cost. And land locations south of Hannover are poor conditions for wind turbines generally, with few exceptions. In those cases, earnings can be scarce and things can get uneconomical.
Should have mentioned, I'm running testing/unstable. After the stable release, all the new experimental stuff for the next release floods into unstable.
Agreed. The latest Debian upgrade installed pipewire for me, and I didn't even notice, everything just worked fine! And that after years and years of fiddling with alsa and pulseaudio configs, uninstalling pulseaudio, hacks upon hacks to get stuff working with either, etc.
Another copycat change to get the same crappy non-ergonomics in unrecognizable controls as the others. Can we please fast-forward all the UI circus to arrive at something usable again? Pretty please?
The French culture is to never deliver bad news before the deadline has arrived. Underlings will never tell their boss that something is impossible, decisions will be made by grande-ecole-bosses without technical expertise and relationships are valued far higher than knowledge and expertise. You'll always get the first impression that all is well and they'll manage before the deadline. If you need a real non-sugar-coated insight as to how the project is going you need to gather your own data. Discreetly.
However, as soon as shit has hit the fan and bosses got involved, they'll bend over backwards to make things work. But you cannot expect meeting the first deadline, ever. Same for the first budget. Subsequent ones depend on the size of the project.