I've had jobs where we used a containerized dev evironment like this. I've had others where we just installed all the dependencies to our dev machines. The cont

I've had jobs where we used a containerized dev evironment like this. I've had others where we just installed all the dependencies to our dev machines. The container environment is hands down the worse experience of the two. Similar to this tutorial, if you don't want to use the blessed editor, you end up maintaining your own docker container. Similarly if you want to use tools not installed into the official container (say, ripgrep). I'll take updating a dependency on my dev machine every now and then (which could be largely eliminated if we had used something like conan) over maintaining my own docker image any day. You can also largely eliminate relying on system headers through --sysroot, which cmake supports. Another issue we had, which this tutorial doesn't appear to address, is that these containers run as root, so files created in them on a mounted folder easily end up as owned by root. Which can create all sorts of mayhem. The only reliable solution I have seen is to dynamically change the container users uid and gid on login, but this often doesn't seem to get implemented.