Fun fact. Just as this story was unfolding, I was installing a Debian system on an Acer desktop machine. The Debian installer wouldn't start with secure boot enabled because of this, but also, once I fixed up things, I couldn't get the firmware to recognize any entry added by Debian. It would hide and deactivate them on its own. I ultimately had to use a copy of the EFI partition on a USB key for it to work.
Probably unpopular opinion: git submodules are just fine. They're "just" lacking a consistent UI. They have improved over the years, but the default config sucks because the defaults emulate the original, awful, UX. With proper configuration, it's much better, although there are still pain points (like rebase conflicts in non-submodule parts messing things up if you don't git submodule update)
I was like "how the f* is a website builder possibly worth $23B" and then I realized Wiz is not Wix. And then I realized Wix has a market capitalization of $9B, and I'm still WTF.
Linking does not expect a full and complete so. That's what it's currently fed, but it's not a requirement. You could just as well have "import libs" in ELF too.
The keyword is "arbitrary". Say you have dependencies on reqwest and clap, want to dynamically link against them? Not gonna happen. That's what people talk about most of the time for static vs. dynamic linking, at least in my circles.
That's kind of a disingenuous take. Rust supports producing dynamically loadable libraries. It doesn't support dynamically linking arbitrary dependencies, which is what most people would understand from "Rust supports dynamic linking" in a discussion about static linking.
On top of what sibling comments mention, another common problem is that the STL has many different implementations with different/inconsistent performance profiles. If you want containers with guaranteed performance characteristics, you're better off using your own or a third party.
Here's a story from more than 25 years ago. A user couldn't print a document and calls local support. After they try several things remotely to no avail, the support person comes to the user's desk. Turns out there was a popup window asking the user to put paper in the printer and press ok to retry. How they missed this obvious thing (it was even a MODAL window) is a mystery.
I guess you're being downvoted because of how you said it, but you're not wrong. I have a Japanese keyboard too, albeit not a Mac one, and the underscore needs shift (without shift, it's backslash, which means that yes, I don't need to use M-¥). Caps lock is also under tab, and Control on the bottom left.