Fiberglass repair is quite well understood. Part of the problem is some early turbine blades used wood cores which are incredibly difficult to repair. But if they used synthetic cores (coosa board) they'd have a stable core to repair for centuries.
Maybe they figure it costs more to repair than to replace, which could easily be true. Either way it's not a huge problem, look how much the average American tosses in the trash every week. But I'd still like them repaired
Running them at a pre-determined RPM constantly can resolve lack of VVT, but that limits their applications. New materials for apex seals being researched could alleviate their longevity issues too. But, I have a big soft spot for rotaries and would love to see them applied more :(
Didn't see your reply - but terraform can do a bit in the space of multi-cloud provisioning. I say a bit, because most of the work will be on the user, as your terraform plans are gonna be -MESSY- to support multi-cloud. It really isn't seamless or easy in my experience. AWS and Azure operate with enough differences that you'll have more exceptions to your workflow than actual steps. I find multi-cloud to be burdensome and an awful experience in general sadly, even with the "best" tools.
GMRS radios also barely with within an EV vehicle surprisingly. Was only a few car lengths behind friend on a road trip, couldn't talk to them over GMRS radio, but I could pick up truck and boat traffic from miles away! We had to go back to using our phones to coordinate pitstops!
But it's a feature that comes in quite handy, for only a few dollars of manufacturing cost. I tune to road status AM radio all the time when driving over the mountains
Most terraform flows are just as trivial as any workflow, create/update/delete of infrastructure. Not like we haven't had a hundred frameworks to accomplish that over the last few decades of onprem. Short term enterprise memory just believes there's only one way/place to do that now.
So much this! PXE is apparently too hard for engineers to learn to bootstrap a VM, but they'll go to $5k worth of training to learn Terraform to deploy a CRUD app and call that a win :/
If it's anything like BetterHelp, you'll just be scheduled to the first available, lowest cost provider who get paid half or less the market rate for professional care. And knowing Amazon, they'll innovate newer ways to make it a dystopian dehumanizing process that leaves all parties with less care, less money, except for the shareholders.
Ageism is too much of a thing in tech. These young frontend js developers can't even hold down F2 to enter the BIOS. So much knowledge lost from companies letting decades worth of experience walk out the door. And it shows, so many modern products have shite architecture.
I was driving behind a Tesla which I can only assume was on FSD mode down a narrow side street coming up to a turn to a busy intersection. The car/driver almost drove straight into cross traffic, ended up blocking a lane without moving for like 15 seconds before it turned right (while signalling left) and almost crashed again into the oncoming traffic coming the other way. Seriously unsafe
You don't have to explain the perils of extending L2 over any type of WAN to me. There used to be a hard requirement from some SANs to have dark fiber for their replication - not just L2 adjacency (needed actual FC zones extended to another site if I recall). But all is not happy times with L3 links and BGP between things (and even then, BGP configs to achieve anything decent in terms of failover needs BFD or more). But sure, poop all over this fun thought experiment if you want, I doubt anyone's going to deploy this and put a billion dollar company at risk.
I didn't say "this solution is easier", simply said someone might find a use case for it. Ya'll are dismissive of something neat with a number of use-cases (I only tossed out just one use case that popped into my head, based on actual experience on a million dollar SAN, that is still supported (and sold!) to this day).
There's a number of specific scenarios this could be useful, like, some SANs can only replicate to L2 adjacent units. Say you wanted a replica off-site, and your gear is older/proprietary, you used to have to buy enterprise network gear to encap L2 and ship VLANs to remote sites. I wouldn't be dismissive of using VXLAN over wireguard to accomplish that.
There are a lot of words on this blogpost (is this is a blogpost? Or some company announcement?). I'm not sure what any of it means, the person sounds unhappy with their job (even says their job did not bring them joy!). Seems really odd to write all this stuff about... finding a different role in a company? And whats all this waifu stuff? Is this a trend I've missed?