> What kind of workloads spawn so many processes that saving microseconds becomes relevant?
With a huge process, you have a timeframe between the child is spawned and it executes exec*() where you typically "do stuff" (such as closing a lot of fd)
During this timeframe the parent process has its universe COW'ed, and each write will trigger a page fault.
The performance impact can be concerning in the _parent_ process.
> Because nuclear plants are expensive, and they take a long time to build, financing their construction can also be a significant fraction of their cost, typically around 15-20% of the cost of the plant. For plants that have severe construction delays and/or have high financing costs (such as the Vogtle 3 and 4 plants in Georgia), this can be 50% of the cost or more.
This is why nuclear power plants should be state-sponsored projects. States typically have loans at 0% rate, or even negative interests.
The issue with posix_spawn is that you can't close all descriptors before exec. This is especially an issue as most libraries are still unaware they need to open every single handle with the close-on-exec flag set.
It's inherently inefficient because while the child process does its initialization (pre-exec) stuff, the parent gets page faults for every thread writing into the memory due to COW. This will basically stall the parent and can cause funny issues.
You simply can't. The constexpr environment won't let you have uninitialized variables/memory anywhere. It won't let you access dangling/out-of-bounds pointers either, overflow two-complement types, etc.
> C++ was discussed as having too many undesirable characteristics.
I tend to agree, as a C++ developer. There are many core issues in the language that haven't been resolved and that are unacceptable for kernel code.
My personal pet peeve: C++ is unable to reallocate a new[] region. This makes basically all structures (vector, hashmap, trees...) unusable for large data handling.
> The biggest retaliation the West can make right now is a commitment to a rapid exit at unprecedented speed from the oil economy, in favor of renewables.
You can't exit from the oil economy with renewable such as wind or solar due to their non-predictability.
If you want to stop importing Russian gaz, you need nuclear energy.
Same experience with a bunch of Aquantia AQC-107 (ASUS XG-C100C). Had to remove them from a Linux server, it just won't work and botch IPv6 traffic (especially routing advertisement notices ?!). Got Intel x550t2 and all the issues miraculously disappeared.
> The first time you load many common filetypes (like Java for example), a box pops up saying "Do you want me to install a nice set of standard Java plugins?"
This. Used Emacs for fifteen years professionally, and I gave up when I had to reinstall my laptop, as having intellisense-like features and easy navigation in Emacs is a complete pain.
I actually did not intent to switch to VSCode, but after a couple of hours of scratching my head with list configuration files, I ended up "trying" VSCode, and after a couple of _minutes_, everything was working (completion, navigation etc.)
After a couple of tweaking, clangd was plugged, and I had direct visual compiler feedback in realtime while typing code in the window.
This really depended on the university. Some of them were not affected at all, some other had sections where you could not do any research or teaching without being from the "right obedience" (communist, Maoist, etc.)
> They'll eventually come for you too no matter how much you generally agree with them.
Reminds of the Maoism movement in European universities (such as in France) a few decades ago, where people critical of Mao were harassed and treated as fascists. With some universities would make Maoism a de-facto precondition to be accepted as researcher.
This seems to share the same mechanism: very few righteous people having no longer any morale compass due to ideology, and cowardliness of the rest of the herd (including the administration) that refuse to stand for reason and logic.