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.


Don’t know for sure. It’s the 1000w, 12 cup model. It mainly has issues when I’m chopping something dense with the standard blade.
It won’t jump off the counter, but if I don’t have a hand on it, it will shift and try to “shake” walk away.


While I second the breville recommendation in general, I have the Breville food processor. It’s lovely and does everything, but it’s not heavy enough. It’s heavy, but lacks the real weight it needs to counter its serious motor. I have to hold it while using it, which makes it cumbersome.
It does an excellent job, especially at grating and slicing with its adjustable disc, but it annoys me enough that the blender gets used as a food processor more often than it should.


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.