The future is in containerization anyway. If we all run Qubes OS, we can run each vibecoded project in separate containers. So when they crash and burn, we just restore from snapshots. The future where noone does long division is inefficient!
So you can run the same functionality on 100x the computing power? Seems as reasonable as rebuild a motorway bridge out of burning toothpicks each time a car wants to pass. 👍
Depends on your threat model. For someone who works in cybersecurity, the hard seperationo files per-project, easily split networking to different VPNs between VMs, and being able to keep sensitive data on a basically air-gapped VM that you can only copy to clipboard from is amazing. And with templates getting a stack of VMs for a new project running is pretty quick.
QubeOS is one of the coolest OSes around, if you work for multilple customers and/or take your data security seriously.
It’s true that I have not considered it from the AI-slopworks PoV, but in general doing development in a container is probably a must nowadays anyway, so why not have a system build around it. It’s not like virtualization is any difficult.
I would say that building a container for developments becomes worth it once your project reaches a certain scale and has lots of environment variables/input or when you want to produce reproducible builds. For smaller projects or projects that have a relatively low threat level it may not be feasible to create a virtual environment.
The future is in containerization anyway. If we all run Qubes OS, we can run each vibecoded project in separate containers. So when they crash and burn, we just restore from snapshots. The future where noone does long division is inefficient!
So you can run the same functionality on 100x the computing power? Seems as reasonable as rebuild a motorway bridge out of burning toothpicks each time a car wants to pass. 👍
Depends on your threat model. For someone who works in cybersecurity, the hard seperationo files per-project, easily split networking to different VPNs between VMs, and being able to keep sensitive data on a basically air-gapped VM that you can only copy to clipboard from is amazing. And with templates getting a stack of VMs for a new project running is pretty quick.
QubeOS is one of the coolest OSes around, if you work for multilple customers and/or take your data security seriously.
It’s true that I have not considered it from the AI-slopworks PoV, but in general doing development in a container is probably a must nowadays anyway, so why not have a system build around it. It’s not like virtualization is any difficult.
I would say that building a container for developments becomes worth it once your project reaches a certain scale and has lots of environment variables/input or when you want to produce reproducible builds. For smaller projects or projects that have a relatively low threat level it may not be feasible to create a virtual environment.