Look, if you willingly have any piece of your stack relying on Microsoft you have to be ready for the rug pull. They WILL fuck you, it's guaranteed.
Then they will gaslight you.
Microsoft subtracts C/C++ extension from VS Code forks
21–30 of 354 posts
Re: Microsoft subtracts C/C++ extension from VS Code forks
#22Look, if you willingly have any piece of your stack relying on Microsoft you have to be ready for the rug pull. They WILL fuck you, it's guaranteed.
Not to quibble, but VSCode (and GitHub for that matter) are part of my tooling, not part of any of my stacks. To me the former is tolerable, the latter is not.
I think they are talking about products like Cursor.
Re: Microsoft subtracts C/C++ extension from VS Code forks
#23Do you guys ever feel tired of 'sounding the alarm'?
I feel like I've been doing that for years on a wide range of topics, but every time it's like you're talking to cult members.
How do you break through to people? People say things like "you're overthinking it", "that's never going to happen", "I don't care because I like using VSCode and not alternatives".
Is it individualism? That they only consider their own narrow short-term interests, and have become blind to collective problems?
Re: Microsoft subtracts C/C++ extension from VS Code forks
#24The intellisense from clangd is much better and faster than the Microsoft C++ extension, if you can set up a compile_commands.json. Although debugging still relies on the Microsoft extension. Although I don't think it's going to be hard to create an extension just for debugging (if it does not already exist?)
Yes, even on medium sized code bases (few 100K lines), the Microsoft C++ extension gets extremely slow. Clangd is a much better option.
Re: Microsoft subtracts C/C++ extension from VS Code forks
#25Good. Now it's time to learn from this important lesson.
Re: Microsoft subtracts C/C++ extension from VS Code forks
#26Re: Microsoft subtracts C/C++ extension from VS Code forks
#27Glad I'm using Sublime Text.
Re: Microsoft subtracts C/C++ extension from VS Code forks
#28Look, if you willingly have any piece of your stack relying on Microsoft you have to be ready for the rug pull. They WILL fuck you, it's guaranteed.
Anything that’s not gpl-licensed is going to pull the rug from under your feet, people should have learned this by now. Also, if you do open source contributions, never ever agree to assign copyright to the project: doing so means the project owners can relicense the code base, even towards proprietary license.
Absolutely. I signed one copyright assignment, ever, with the FSF. I trust them enough to do that, but they're just about the only ones.
Re: Microsoft subtracts C/C++ extension from VS Code forks
#29The hilarious part is that old fart C++ programmers (like me) have been the ones most leery of VS Code. Microsoft’s gonna Microsoft, ‘specially with compilers.
"Don't be paranoid", they said.
"That's ancient history", they said.
"Lucy will hold the football this time for sure", they said.
Re: Microsoft subtracts C/C++ extension from VS Code forks
#30Earlier quoted context omitted.
I think they are talking about products like Cursor.
Ah, that’s a painful situation.
Eh MS wasn’t going to just let VSCode derivatives soak up all the AI gold rush money, these companies knew the risks. I wonder what it’s going to mean for projects like Zig, a migration of VSCode refugees could crank things up to 11 pretty quick.