> This also means that everyone get the same tools (same version, same bugs).

Everywhere I've worked solved this by having the toolchain available via a network share that you would mount/copy, or checked into p4 so that everyone would be on the same version and you would know what compiler version was used to build a particular release. I suppose you could achieve the same thing by building in a Docker container..

This is kind of the idea behind the hermetic environments that Bazel enforces, and is essential if you want bit-for-bit reproducible builds.

Yeah, but everything is easier if it's native to your machine :)

We have used Docker images in past but it gets really annoying with large code trees and access permissions for programmers and debuggers...

Just a small correction:

>on Windows you need to download and update it manually

you don't need to update it manually, it will show a popup that an update is available and will update itself once approved.

It used to direct you to their website to manually download and install it. Given how often it is updated most people started ignoring those pop-ups.

Maybe that used to be the case? For at least the last few VS Code updates, it's been entirely in-app. The update is downloaded in the background, and VS Code then prompts you to restart the app to apply the update.

is there any debugger as good as the Keil IDE in Linux?