I work in HPC and at some point we had a dozen or so racks with blade systems in our cluster. IIRC it was HP c7000 blade enclosures, 16 nodes in a 10U chassis. We had 4 such chassis in each rack. So reasonably dense, and there was a bit less cabling compared to individual servers.
OTOH, much of the cost saving of less cabling was eaten up by the vendor charging higher prices for equipment like HCA's or switches compatible with the blade enclosure. And unless you went for a fully non-blocking IB fabric there were a bunch of unused IB switch ports.
Also, while the blade enclosure had this fancy web GUI for management, at scale we had built our OOB management automation around IPMI anyway, so this wasn't a feature worth much for us. If anything it was a bit of a chore, as in the cases when we needed to do something which IPMI wasn't capable of, there was an extra step of figuring out the node->chassis mapping to know which chassis to connect to, and then figuring out which blade in the chassis corresponded to the node in question.
For the next generation we got these "twin" systems manufactures had started coming out with, with 4 nodes in a 2U chassis. A bit more cabling than the blade systems, but in the end it was somewhat cheaper.
Here in Northern Europe there seems to be something of a renaissance of traditional linseed oil paints, both because of people being more environmentally conscious and wanting to avoid VOC's and microplastics, but also because there's plenty of scare stories of people rotting their houses after painting them with more modern but less breathable paints like the usual alkyds or acrylics.
Not saying it's not possible to be successful with the modern paints, but they demand a different style of construction that allows air to flow on the backside of the facade.
At no point should you (nor would it be physically possible to) set the yards in the direction of the ship. At most during sailing they would be turned maybe 45 degrees which would correspond to "close hauled" at which point you may be able to reach about 60 degrees from the wind direction.
Thus, a simple linear function that would show the optimal angle of the yards as a function of the wind direction (0 = wind straight ahead, 180 = wind straight from behind) could be something like f(x) = -3/8 x + 67.5.
And as a slight visual cue, please show the mast when it would be visible before the sails as well. I found that I was often confused whether I had the yards sheeted all the way one way or the other way.
Also I think it would be clearer to show the yard position indicator as 0 degrees when the yards are squared, that is perpendicular to the ship. Then sheeted to the maximum would be 45 degrees either way from 0.
Rust and Ada are about equally safe, both have advantages and disadvantages. Perhaps you're thinking about SPARK ADA, but that's a different kettle of fish.
It's a bit like saying you should program in C, because formal verification tool X generates C code hence C is safe.
But thanks to the magic of the Interwebs, most of those jobs don't have to be in the city, region, or even the same country as the one where the DC is located. So for a local politician, most of those jobs won't get them reelected.
If the owner of the stack (Logio or whatever it was called, see upthread) doesn't understand it, the consultants will run wild and soon it will require a hectare-sized datacenter running a zillion containers, and another DC for HA of course.
Which in turn relies on a stack largely written in, shock and horror, C, such as the Linux kernel, libc, openssl, nginx, etc. etc.
Even if you believe language X to be the bees knees, are you going to stop using it until everything below it in the computing stack has been rewritten in X? Of course not.
The question is whether the current situation is a short burst of action, and once those most critical bugs get fixed the hype around AI vulnerability scanning will die down, or whether the current crop of system/infra software written in vulnerable languages like C are beyond redemption and they will provide an endless source of critical bugs for AI to find until we fix them by rewriting them in Rust/Go/whatever.
The Linux kernel is another example. The 2.5 development cycle (which led to the stable 2.6 series) was brutally long, and distros resorted to back-porting new features into their own kernels based on the stable 2.4 series that they provided to their users, creating all kinds of excitement. After 2.6.0 was released, Linus basically went nope, not gonna do that again.
$50M? Pfft. The regional health service provider over here has spent close to a billion € migrating to Epic over the past decade. The feedback has been so devastating they're apparently now considering starting over from scratch. Love seeing the consultants lighting my tax money on fire like that.
For comparison, latest commercial turbofans approach 6000h (they don't have a strict TBO limit AFAIU, overhauls are decided based on various inspections and measurements). At a typical airliner speed that's something like 3,000,000 miles.
Many developing countries, however, were able to leapfrog the wired phones stage.