VS19 SUCKS FUCKING ASS

Just kill it off already.

Make a compatibility version for the wage slaves and use a modified VS Code as the Windows IDE going forward.

Just use Xcode instead.

>>2
I wish. Sadly the world runs on old java and c# software.

>>2,3
Is Xcode that good?

>>4
No idea. But it can't be as bad as VS.

Also I imagine you can get around it better than on windows were you can't ignore it. You couldn't even install the compiler without the IDE for some time.

>>5
VS 2005 was ok. I know that software tend to worsen so it's indeed possible that VS 2019 "sucks fucking ass."

VC6 is the best version.

VS Code

Fuck no, that's even worse.

>>7
It's unironically much faster than VS. Imagine how big of a fuckup you've to be to lose to electron.

WPF sucks ass and so does every GUI toolkit that isn't written in C. That's why they all died. Good riddance.

just downloaded VS2019 community today to port some code to the latest version

decltype(int{ (void*)nullptr }) x = 0;
int y{ (void*)nullptr };

both lines should be error, and are on vs2015 and 2017, but the first line compiles on vs2019. what a shit.

>>9
Yea, same. We started some projects using .NET Core so I've to use this garbage.

I just think the VS team has to justify their pay or entertain the interns/juniors. There are no upsides to VS19, but a shitton broke or got slower. When writing cshtml I constantly have an yellow exception message at the top of the editor and SOAP doesn't work at all anymore. But the worst thing is that every action takes an eternity. Right click on the file drawer? Wait half a second for the menu. Touch a clean file? Wait 5 seconds for visual studio to catch up.

I'm honestly trying to get out of windows dev only because of VS being sucky. The heartbreaking thing is people don't care, they just suck it up.

What is the issue with VS, >>1-kun??

but the first line compiles on vs2019

Usually people complain when code doesn't compile. This is the first time I've heard the opposite.

>Windows
found your problem.

>>11
It's slow.

Shouldn't get to me though. I'll log off.

What Nikita's blog post is this?

cope

you just hate programming (rightfully so) and are misplacing your resentment on the tool

VS is the best Sepples IDE on the planet

>>16
Are you kidding? VS takes like 30 seconds to open one solution.

I use Sublime Text for our complete monorepo and it takes 0 seconds to open the monorepo sublime-project and 0 seconds to open a cold file from the file drawer. The only lag I experience is when there's a fat tree in the file drawer and you expand it it which takes like 0.5 seconds which doesn't feels responsive. At this point I only use visual studio to do edits and use sublime to navigate and read the code.

But I guess sepples programmers are accustomed to eat shit.

It's embarrassing: The people making Fortnite, a children's toy, manage to draw a massive amount of data in 200hz+ and manage input, input of 100 online players so that everything is silky smooth, but the retards at the vs team don't manage a syntax recoloring without locking up for 2 seconds.

>>12
It's gay because it fucks up techniques like SFINAE that depend on the first line being an error. Code might use decltype or void_t, etc., to check whether that line is an error and do something different if it is. But if it compiles in the check despite the actual code being an error when it is actually used, then the choice becomes ambiguous, or you get into a situation where the compiler tries to make a choice based on the code in the decltype not being an error, but it turns out to be an error when it hits the actual code outside the decltype so your build just fails.

For non-sepples people, to explain how retarded vs2019 is by acting this way, it basically boils down to having a feature like "bool willThisCodeCompile(string code)" and then having a case where that feature returns true for code that won't actually compile.

>>17
>The people making Fortnite, a children's toy, manage to draw a massive amount of data in 200hz+ and manage input, input of 100 online players so that everything is silky smooth, but the retards at the vs team don't manage a syntax recoloring without locking up for 2 seconds.
You're criticizing sepples, but you do realize that this is because Fortnite is written in sepples while VS is written in a mishmash of smelly dumb dotnet scum languages, right?

>>19
I just noted that sepples programmers are accustomed to eat shit. You would think that knowing that software doesn't have to be smelly shit they wouldn't call vs ``da bes sepples IDE on the planet".

Of course Fortnite is written in sepples. All good software is.

>>20
Okay, just wanted to make sure.