Microsoft Teams is dog shit
That’s all.
EDIT: Thank you all for detailing your experience with, and hatred for, this miserable product. Your display of solidarity is inspiring. Now, say it with me:
Fuck Microsoft
You are viewing a single comment
That’s all.
EDIT: Thank you all for detailing your experience with, and hatred for, this miserable product. Your display of solidarity is inspiring. Now, say it with me:
Fuck Microsoft
VS Code. That's it though.
You may know already, but you should try VSCodium. At least they took the Micro$hit telemetry out!
Powertoys too
That's open source though?
Indeed https://github.com/microsoft/PowerToys
Ah yes, you're right.
I guess a better qualifier might be: closed-source Microsoft products tend overwhelmingly to suck.
VS Code is OK if you can't afford the JetBrains ultimate subscription. I never want to see a VS Code launch configuration again.
Fuck subscriptions though.
Agreed...the community editions of their tools are solid, but if you're doing cloud stuff, get your company to pay for it. It blows VS Code out of the water.
Ehh, it's ok in the case of JetBrains - if your subscription lapses your license converts to a 'perpetual fallback license' so can just continue using the version you installed when the subscription was originally purchased.
I'm using a 4 year old version of PhpStorm with no issues and no subscription. My PyCharm sub ended 6 months ago and I'm staying on the 2023 version of PyCharm because the latest version comes with lots of AI which makes my CPU fans scream continuously.
WebStorm and Rider will have community versions soon, they are going to eat VS Code's lunch.
They've been cramming random stuff in that though that's making it more laggy. Recently switched to Zed and it's so much faster.
WSL was my gateway drug to Linux. It's neat. Until it isn't.
TypeScript isn't terrible. It's extra work to set up, but it makes JavaScript codebases somewhat more maintainable.
Visual Studio for live .NET debugging and the WPF live editor.
Some C/C++ extension process once reduced my laptop to a crawl, and I couldn't close VS Code, so I killed the process through the task manager, simple enough, right?
Long story short, I started smelling burning plastic and saw that, somehow, there was no VS Code process, but the extension had a separate process that was still running at full speed doing idk what. I almost burned myself when I picked up my laptop. So I'm not very happy when I see VS Code
Your laptop caught fire while running vs code it had nothing to do with it, it doesn't have a "burn my laptop" function.