User reports that expanding folders in the solution explorer of VS Code with the C# Dev Kit is slow on a MacBook Pro M2, even with a project of 130k lines of code. They request improved performance for basic operations in large .NET projects.
I’ve got one question. Years ago I had an old Acer laptop with 1GB RAM and an Intel Celeron, running Windows 7 and Visual Studio 2008. It was fast, smooth, and reliable enough to work on without any lag. Now I’m on a MacBook Pro M2 with 8GB RAM (macOS Tahoe 26.1), using VS Code for a .Net API + Blazor WASM project. It’s painfully slow — even expanding a folder in the solution explorer takes ages, which is ridiculous for something so basic (C# Dev Kit). I used Rider as well, and it used to be great, but now it’s even worse than VS Code: memory leaks, hangs during builds, and I have to restart it after every 5–10 builds. So my question is: are we missing something here? Why is this happening? Is it just software getting heavier, or is Apple slowing down the system on M2 to push people into upgrading? Edited : my project size : \- 130K lines of code (45K C#, 35K Razor) \- Clean Architecture with .NET 10 + Blazor WASM