> I'm a big containers fan, they work really well (assuming you're not developing with MSVC). They give you a repeatable build environment, which is a boon for something like C where you're implicitly depending on system include paths for versioning.
For development, I actually don't like "repeatable build environments". I like using a different, continuously updated systems, I consider having a different environment for CI/CD and for development to be a good thing. It is one of the best way to test for compatibility problems, a kind of dogfooding.
Plus, it is nice working on a system you are comfortable with, and without the performance penalties of virtualization/containerization.
For releasing and testing however, containers are great.
For development, I actually don't like "repeatable build environments". I like using a different, continuously updated systems, I consider having a different environment for CI/CD and for development to be a good thing. It is one of the best way to test for compatibility problems, a kind of dogfooding.
Plus, it is nice working on a system you are comfortable with, and without the performance penalties of virtualization/containerization.
For releasing and testing however, containers are great.