[korla]

I agree, and the competition is at this point more between VS and other full-featured IDEs like JetBrains Rider, which is my tool of choice for .Net-development.

But, what I didn't know until this recent debacle, is how there is a theory that the reason the .Net-tooling in VSCode is so bad is the same reason we had this watch-debacle. There was some discussion on that in the other HN-thread: https://news.ycombinator.com/item?id=28968231

[vyrotek]

I've become more convinced that VSCode doesn't implement certain features to not compete with VS. For example, support for File Nesting.

https://github.com/microsoft/vscode/issues/6328

For a while there wasn't really another way to run SQL projects outside of VS. Data Studio recently got support for that though.

[lozenge]

I think in this case it's more like "let's not implement something for one language".

In VS the Solution Explorer lists Project Items, not files. Eg it lists DLL References. This means the entire tree view goes through the IVsProject interfaces and you open Solutions and Projects, not folders.

VS Code works on files only and doesn't have a project system that can specify file nesting rules. The simple ask in the PR could be implemented, but it seems arbitrary and other languages will ask for their own rules. (Vue?)

[vyrotek]

I'd personally like it for Angular component files as well. I imagine there are several types of files that would benefit from being nested.