Googlers by default, though, aren’t allowed to run vms (VMware/virtualbox style) on their desktops/workstations.
Googlers by default, though, aren’t allowed to run vms (VMware/virtualbox style) on their desktops/workstations.
there's something to be said for building and running tests in the same environment your service targets. that's usually not going to be macOS or your favorite linux distro.
All the problems that you’re talking about of keeping in sync etc are just non existent. You have root directory /google/ and magic happens there. Look up articles about srcfs, objfs, piper, forge.
I honestly was looking if something exists open source so I can set it up at least for code editing, but all that I saw is just shit. When I compile at Google even using local build everything just works. Code on nfs network share + cachefilesd + all suggested flags for performance, with share at home nas (diskstation) on 1gbps lan + cachefilesd - constant issues like permissions. Simple test of cloning abseil library to that share and building takes 50%-80% more time than building locally.
Same test with qmk firmware spice is just unbearable. Even just doing git clone there is awful due to lots of small files, I guess. Tried cifs - also bad.
They work great in the (strong-internet availability) environments I've used them.
Also, as an ex-googler, I can attest that google's implementation was enough that I never missed local development.
This works great and is basically identical to working on my laptop directly except that my terminal is running over ssh rather than locally.
I love the idea of a powerful remote development machine but I’ve yet to find a tolerable RDP/VNC-type connection, and that leaves either something browser-based (VS Code maybe?) or something like JetBrains’ remote development tools which aren’t quite there yet.
I was speaking about VMware workstation, virtualbox and others. Running them is (was) not allowed