7 ms·
MSFT seems to be a lost cause these days. Whenever I open up VS2022, it takes almost an entire minute to load. As I recompile things, it will fail to report err
by codalan 3y ago
MSFT seems to be a lost cause these days. Whenever I open up VS2022, it takes almost an entire minute to load. As I recompile things, it will fail to report errors, which means restarting the application (which seems to "fix" it).
If I open SSMS, it also takes upwards of a minute to load. Some things I used to take for granted, like being able to see the cursor when scrolling with the arrow keys, instead makes the cursor invisible, so now I have no idea where my cursor lands when I release the key. When a connection to a DB bonks out (which happens at least once a day), it takes another minute to close out my open windows, because each one had an open session and it needs to prompt me on close.
If I open Excel, another minute passes before it loads. If I stupidly decide to change the font for some cells, I expect to see the app lock up for another minute or two. If I want to save the document, I have to go through several layers of menus and garbage just to save to my computer and not the cloud. And then I will still get an alert in Excel that indicates it was unable to save to the cloud and that I need to take some action to resolve the files. The best part is now I can't simply scroll the rows in a spreadsheet in the background while I have another app in the foreground. I have to make another click to bring the spreadsheet into focus to scroll.
If I go into the Azure Portal, I can expect no sane or consistent interface. Components seem to be cargo-cult designed without regard to how they are used. I was looking at some app service logs today, and I'm stuck using their ugly UI, which truncates/hides important data, like the actual log message. The UI is so antithetical to what a logging user interface should look like (think Splunk or Sumo), you'd be better off just downloading the CSV file.
The same goes for build logs in Azure DevOps. It doesn't word-wrap, so now you need to scroll all the way across the screen, line-by-line, to figure out the message. If I click on the Raw Log link, I get the logs, but polluted with ANSI escape codes. If I try to copy the text as is, the UI may or may not select all of it.
And this is just the very start for the disaster that is Azure Portal/DevOps.
And Teams, lol.
When you have to deal with all these problems, all day long, it really starts to sink your productivity. MSFT badly needs a leadership shakeup, but I doubt that will happen as long as Azure is profitable. Until then, I expect to see more decline in the quality of their developer and productivity applications.
- Whinner 3y agoSSMS is become unbearable to open. It's insane how long it takes. Not even to connect, just to get the dialogue box to select an instance to connect to.
- TideAd 3y agoMicrosoft employs a lot of lifers who have no idea how good tooling is on the outside.
- gfsgfjsgsj 3y agoI use XCode, Android Studio and Emacs daily. I'd say all three are C- tools.
- codalan 3y agoPresumably, there were a lot of lifers at MSFT during the Windows 7 years, yet I would consider the software being delivered during that period as being pretty good. The decline happened after they fired off their SDETs and turned their customers into testers. The hyperfocus on cloud didn't help. Neither did the move towards clunky Electron apps, instead of first-class Windows applications.
- red-iron-pine 3y agoPublicly traded companies have to keep releasing. They can't stop at 7, call it a day, and focus on important-but-not-sales-driving features. Lifers may be there still, but they have to march to the beat of the stock market.
- throwaway2037 3y agoOne idea about Excel: Keep it running all the time, with a new, empty doc. Then, you never pay the start-up cost. Laughably, that is my strategy these days. Same for Adobe Acrobat.
- deafpolygon 3y agoVery strange... Excel is one of the quickest apps on my system. It takes a second to load, if that.