Story of my fucking life in one fucking sentence:

"Visual Studio is not responding"

Ha! I was contemplating writing a rant about this about 5 minutes ago because it happened again to me.

Use an alternative ? Like rider

@Jakuho just moved from vs to rider, and it feel great. But it take way more ram so wouldnt it stuck more the less ram you have?

@hubiruchi from my experience (when i was on windows) VS ate more ram than rider so it's weird.. Is it that much more ?

What's even worse is when VSTS/Azure DevOps fails to load like every 20 minutes

Is Rider (first I've heard of it) an alternative to Visual Studio Code, or the full Visual Studio IDE like 2017? I greatly depend on the latter, so if it's a lightweight editor it won't work for me. I'd Google it but I'm on the road presently.

@duckWit full ide.
@Jakuho yeah, like up to around 1gb ram. You can configure the heap size though, so that what I will do if I have problems

@hubiruchi wtf when I was using it, it was about 500mb, while compiling. Definitly gonna try again and see if i get the same

I installed the evaluation of rider today. Seems sophisticated enough. Little nuances give a bit of a learning curve though that I'm just not sure I want to embrace right now. I have been using visual studio heavily for the last 11+ years.

Vim is love, vim is life.