4 ms·
> This isn’t to be polite or to make money — it’s to foster adoption among developers, which drives sales. I get that in theory… and it makes sense most of the
by mbreese 3y ago
> This isn’t to be polite or to make money — it’s to foster adoption among developers, which drives sales.
I get that in theory… and it makes sense most of the time. I’m not sure it does this time though. You don’t exactly “target” Oxide as an OS or platform. Rather, you use it to run VMs on. Those VMs are whatever you want. Other than that, I’m not sure what else having a home-lab version of Oxide would look like.
A different competitor to Proxmox?
- amluto 3y agoPeople target AWS and GCP and Azure, and they write actual code that interacts with them, do test deployments there, and do real deployments there.
- mbreese 3y agoRight, but you need to be at a particularly high scale when you need to write code that directly interacts with a cloud provider. I can think of no use case where you are at that level that can also scale down to a home lab setup. Yes, you can do slimmed down cloud deployments, but you're still not running the (actual) S3 or EC2 backends at home. At most, you’re talking a K8s based deployment (for a workload that could scale up or down). But that’s also not at the level of working with Oxide directly. And I doubt Oxide wants to get into the business of selling access to their own public cloud.