I go back and forth between a personal Debian box and Surface laptop all day long and it really just emphasises the amount of bloat and drag that Windows experiences doing even the most basic things like manipulating files and using a web browser.
I can use VS Code on both OS's and everything is faster on Linux. Not sure why I would choose Windows unless I needed the C#/.Net toolchain.
My latest issue is a clean install of Ubuntu 20.04, 20.10, 18.04, all have screen flickering. Which doesn’t occur in other distros. (Not screen tearing)
But if I try mint, it has random UI freezing. Pop_OS! Has random things that won’t install because the distro name is pop and not ubuntu. Kubuntu runs flawlessly but then I can’t sign into vscode sync out of the box.
But when it works, it’s awesome.
Unless you're working on a legacy .NET Framework application, .NET Core will happily work on Linux.
For now.
You're missing out on Visual Studio... for Python, C++, etc.
As for VS being slow, it mainly depends how big your project/solution is. Where I know it can be unreasonably slow is when you have lots of projects (several dozen) and you're trying to change all their settings, or something like that. However, if you're referring to the startup time specifically, it might actually be due to your computer not having generated the native images yet (try running ngen.exe executeQueuedItems for both 64-bit and 32-bit). If you mean editing source code, it shouldn't be sluggish at all. But if you mean features like Find Reference, Go To Definition, etc., those rely on Intellisense which takes a while to update for a complicated language like C++ (or a dynamic one like Python)—I don't expect much variation across IDEs here.
___________________________
UPDATE: I think you deleted your reply, but I replied to it already, so I'll paste it here:
You're talking just about when you hover on the tool tabs, right? (i.e. the delay should not be there if you click, right?) It takes 400ms to open by default because that's the default menu show delay on Windows. It's the same delay you see if you right-click inside a folder and hover on New, for example. The delay actually works well for menus for older folks/non-techies, but it's glacially slow for developers (including for menus) unfortunately. You can reduce the delay by changing
HKEY_CURRENT_USER\Control Panel\Desktop\MenuShowDelay
I can't speak to what CLion does with the memory you give it, but it's generally bad for programs to take up arbitrary amounts of memory, given that'd deny the memory to other apps. I wouldn't judge a program positively if it takes up more and more memory the more I give it.
For the ngen thing this is specifically what you want to run:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\ngen.exe executeQueuedItems
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe executeQueuedItems
As to what you're missing by using CLion, well the first thing is the subscription money and the second thing is that it doesn't support nearly as many languages. Beyond that, I'm not sure I can give an accurate response right now because CLion has changed a fair bit since I last tried it, and added new features it didn't use to have before. I know one thing I can think of off the top of my head is that CLion uses Make and/or CMake, both of which have so many rough edges (like relative paths, paths with spaces, etc.) that anything based on them turns me off a priori (and in fact terrifies me because it means my files might get accidentally wiped). Other than that, I'd have to try it again myself and see what might have changed. You should just give both of them a real try and compare; you might end up liking both for all I know. But I can't think of anyone I know who's given VS a real chance and disliked it—the only exceptions I know are people who just hate it because they hate things Windows things altogether.