2 ms·
To be honest, not needing to write legacy C# and C/C++ applications have replaced VS for me. It's not a replacement for VS itself in that regard, but the activ
by oneplane 5y ago
To be honest, not needing to write legacy C# and C/C++ applications have replaced VS for me.
It's not a replacement for VS itself in that regard, but the activities that used to be bound to that IDE moved on over the years.
Whenever I have to load some old project into VS, it feels old, slow and clunky compared to other tools. The limitations on the structuring on-desk, metadata, building, linking etc. are very annoying as well for projects that ended up having more than just generic Windows Desktop targets (or even if they are highly specific editions/versions). I suppose that might be because other tooling outside of the process of the 'write-debug-release' chain has moved to broader and more interchangeable concepts where VS has remained basically the same for the last decade.