@Brett Saviano 

Hi,

answers to your design questions:

1. I'm good with the VS Code explorer. The only issue I encounter is that sometimes either due to desync of some sort or because of file/class renames, my local does not match up to what is on the server. The InterSystems Explorer does show that files are on sever but not on disk, but it does not seem 100% consistent.
2. We don't use DFI
3. For me no, I'd rather like the sever to always match what is on disk, including deletons and renames
4. Anything that keeps the server up-to-date with my local changes is welcome and should be enabled by default IMHO

Might be off-topic but I'd love it if I could use a client-side code formatter such as Prettier. To my knowledge the server formats the code and we have little to no control over that.

Also in the realm of off-topic stuff, we like to use "objectscriptQuality for VSCode" for ObjectScript linting and I have wondered if this isn't something that should be handled by the InterSystems team. From my own digging this extension uses a branch of SonarLint that it bundles along with the ObjectScript lint rules, haven't had any problems with it but I thought I'd raise it up with you guys for a professional opinion. I don't like the idea of having two versions of Sonarlint runnig in parallel (one for ObjectScript and the latest for our other languages). Maybe i'm just off my rocking chair though.

Joel