Visual Studio 2022 | Hacker News Reader

Visual Studio 2022

visualstudio.microsoft.com

32 pointsdgellow16 comments

It's frustrating that Microsoft is putting resources into Visual Studio 2022 when their current version, 2019 never really got out of the Alpha stage.

In particular, things that really should take microseconds can take minutes. E.g., just starting the fucking editor

Virtually every feature seems closer to a MVP implemetation; nowhere near the "good enough" stage

Just my opinion

My opinion is that there is something else wrong if your editor takes minutes to open.

I know very few people that routinely have major issues with VS. It's not perfect, but it's a really good IDE to use and to be really productive given the appropriate workload.

Mine takes about a minute to open. It is good once open until I try to debug an asp.net application - then it slows down. Its even worse if one of Microsofts default app monitoring/reporting library kicks in during debugging - lots of realtime graphing et al that I never asked for.

I hope VS 2022 works out but I am concerned about load.

It's not just an opinion - VS2019 is noticeably slower than VS2017.

Visual studio is a pretty nice development environment. However, when compiling c++ software it routinely takes much longer than compiling with make on Linux on the same hardware (dual boot). Close to 10x longer! This is with cross-platform cmake projects. Anyone else experience this?

Just speculation here, but I suspect the time to compile has little to do with the complier, but rather the way Visual Studio is architeched. There are layers-on-layers of half-assed fuctionality build on top of everything in VS.

While you might want to just compile a release version your program, Microsoft has other priorities. Initialize profilers, networking subsystems, debugging support, check the internet for whatever-the-fuck, check drivespace on drives you're not using, see if bill gates' dead grandma's cookies have been delivered...

Just speculation here

Exactly, and not really correct. Building on the commandline, no VS used at all, still has the same problem. It's really just the compilation istelf which is the main factor.

Are you running an antimalware program with real-time scanning enabled on Windows? I've found that typically causes a lot of the slowdowns on builds if you don't have your worktree excluded from it. Linux still ends up faster for me even without the anti-malware on Windows but its not as dramatic.

There is the normal windows defender active, but unfortunately I don't have the permissions to turn it off or set exclusions.

Are you a developer who doesn't have admin rights on his machine? How does that happen?

It is possible to have admin access, but still be locked out of certain things via group policy.

There may be other anti-malware, file encryption, etc installed without your knowledge or visibility.

Yes, I have the same experience. Using the same version of clang to build the same software on the same computer / same SSD than Linux is muuuuch slower on Windows - win32 is just incredibly slow and has not kept up with the times, especially for filesystems and scheduling

For C++ development, MSBuild sucks and the IDE for code authoring is slow and cumbersome, but the debugging experience is still king; there is nothing that even comes close on any platform.

I wish we'd get the debugging experience ported as an extension in VSCode and (wishful thinking) cross-platform too.

Is there a Chocolatey package for it already?

Not sure but you can get it using winget. Just search via “winget search visual” and you will see multiple entries “visual studio 2022” (pro, community, etc) that you can then install via “winget install <package_id>”

Reply on news.ycombinator.com