3 ms·
It's clear the game is to prolong the lifespan of Visual Studio for as long as is feasible. I wouldn't have any problems with this if Microsoft actually bother
by bob1029 5y ago
It's clear the game is to prolong the lifespan of Visual Studio for as long as is feasible.
I wouldn't have any problems with this if Microsoft actually bothered to make it a good experience. Visual studio should start up in <1 second and not do ridiculous bullshit like change layout every time you start/stop the debugger. Also, woe be unto any developer who decides to build a large, complex Blazor app. Razor component editing in VS2022 is a stoichiometrically-ideal dumpster fire. Select that text in a way the IDE didn't prefer? Prepare for 30s of locked-up circus. It's a Faustian bargain to be sure - Will it come back quicker than if I had just killed the VS process and reopened all my windows? Who knows. I guess I'll wait a few more seconds...
I am really tired of the shitty engineering and lack of focus on the developer ergonomics. It is clear more time & energy went into adding Azure trash into VS than making it smoother to work with. I appreciate all the survey prompts in VS - It makes it look like you are giving a shit, but it is pretty clear that those surveymonkies effectively wind up in the zoo.
My proposal to Microsoft is this: Rewrite the whole thing from zero. Call it "Visual Studio Lite" or whatever. I'll actually pay you for this - if you spend real engineering hours on it and make it the smoothest experience available on desktop. There is no reason Overwatch should be able to run better than my IDE, especially when a trillion-dollar company is involved and is also responsible for the entire operating system upon which these things are happening. The % of features in VS2022 that I need for .NET development today is something like 5-10%. Get rid of the rest for those of us not supporting VB6, et. al.
If the latest language features, libraries & frameworks weren't so amazing, I would have moved to a different ecosystem a long time ago. I'm seriously considering dropping Blazor because the tooling is so trash. I love the concept of how it works, but if it's a nightmare to develop on I'll build a different path.
</rant>
- electroly 5y ago> change layout every time you start/stop the debugger This one is a bona fide feature that I hope they do NOT remove, FWIW. It's switching to the debugger layout, which you can customize independent of the development layout. This is what lets you bring up the call stack, watch, etc. panels in the layout you prefer and it'll remember that, without having them appear during development where they are useless. > Rewrite the whole thing from zero. Call it "Visual Studio Lite" Or, perhaps, "Visual Studio Code"? :)
- nyanpasu64 5y agoI dislike how in Visual Studio, hiding a sidebar or bottom panel requires closing every tab, or marking every "split" as autohide. And showing the sidebar requires reopening every tab, or marking every pane as docked. And you have to do this separately in edit and debug mode. Jetbrains does okay, since you can use Shift+Esc to hide a panel (I prefer VSCode having separate shortcuts to hide the left sidebar and bottom panel). Qt Creator comes pretty close to working well (having to switch between CMake/build/stdout viewers is annoying, but it's also bad in JetBrains). But I dislike how when I enter debug mode in Qt Creator, I sometimes get a debugging bottom panel over a stdout bottom panel, leaving not enough room to read my code. Then I have to mash Esc to (unfocus the Find bar, close the Find bar,) close the stdout panel, and then stop mashing (because if I press it again, I'll exit debugging mode).