Only if you engineered your stack using vendor neutral tools, which is not what each cloud provider encourages you to do.
Then the adminstrative overhead of multi-cloud gets phenomenally painful.
Only if you engineered your stack using vendor neutral tools, which is not what each cloud provider encourages you to do.
Then the adminstrative overhead of multi-cloud gets phenomenally painful.


Meanwhile GIMP out here going “Yup, you got it right.”


No ZigBee, zwave or threads. Only has WiFi/bluetooth built in.
They sell 2 separate antennas that each handle ZigBee/threads and Zwave, respectively for about $100 total.


ZFS has built in error checking and correction if you have parity data. Its less if they have had corruption and more that it doesnt matter, because their system is designed to correct it automatically anyway.
With EXT4 over 30 years, you’ve likely been lucky or unaware of any corruption. Guess thats the same thing in the end.
Yeah, Terraform or it’s FOSS fork would be ideal, but many of these infrastructures are setup by devs, using the “immediately in front of them” tools that each cloud presents. Decoupling everything back to neutral is the same nightmare as migrating any stack to any other stack.