Re: Visual Studio 2013 fast rabbit vs 2026 slow dog
Hmm.... 2013?
Well, for one thing there are some tasks that you simply cannot do. E.g. if you have a server process that is leaking memory. You capture a process dump at startup and one a little later when the leak is noticeable. Since VS2013 is not 64-bit, you had some rather unfortunate limitations if my memory serves me right.
There is also the question of what .net SDKs are supported. The new (and far superior) .csproj project file structure also requires a newer VS.
And although co-pilot can be likened to having a junior dev on the team, sometimes that can be enough. Just make sure you give it exact instructions and spend time reviewing the work. Or just use co-pilot as a more advanced way of looking up intricate problems on stack overflow. Or if you sometimes use a dev language you are not intimately familiar with, it is an excellent way to get started on a piece of code.
As for "fast rabbit", I think 2013 still had problems handling solutions that spanned 100+ projects. That is something that was addressed in 2016 I think. But there certainly is no "the older VS you have, the faster performance you can expect" correlation.
For smaller jobs (e.g. working on a bicep-project) I usually defer to VSCode.
It is difficult to give you a better answer, because there has never been much I missed from older iterations of VS.