171–180 of 354 posts
Earlier quoted context omitted.
cursor also hijacks the 'code' alias to start vscode from the cli, which I use a lot. It's extremely annoying to have cursor start instead and unnncessarily difficult to get rid of. I removed cursor because of this.
"code" is way too generic for a single program to claim exclusive rights to it.
Earlier quoted context omitted.
Now, I get why you made the quip, but I for one keep both of those out of the business I run for this exact reason: I do not trust MICROS~1 in the medium to long term. I also present the CEO and board with other arguments, like moral ones about involvement in atrocities and tyranny, legal ones regarding things like data protection, market related ones such as the likelihood of a future showdown between the EU and US.…
I don't like to be seen as defending Microsoft, they definitely have their share of faults, but as far as business goes, I think Microsoft is the least likely company to screw you over as a (business) customer. Microsoft has kept old software working pretty much unchanged for the last 20 years. I know, I still have software built on early Windows 95/NT4 that works fine on Windows 11...and with some registry tweaks Wi…
As for stability, if you learned GUI Ubuntu twenty years ago you'll be right at home in contemporary Debian systems, while someone hopping from XP or Server 2000 into 10 or 11 would be quite confused for quite some time. Xenial (2016), Bionic (2018) and Fossa (2020) will likely get twenty years of security updates each, into the beginning of the 2030s.
I think something similar holds for the SoftMaker office suite. If you learned TextMaker twenty years ago I believe you'll be less annoyed by their 2024 release than if you learned Office 2003 and get dropped into the 365 style applications. Personally I'd use something else entirely, likely doing a roundtrip through LaTeX or straight PostScript under the hood, but it will be interesting to evaluate some MICROS~1 Office alternatives in my organisation and see what, if anything, sticks.
The clangd extension is better anyway, and is open source. The Microsoft C++ extension is not open source; not sure what people were expecting here.
It's another thing for its license to explicitly prohibit its use with any other IDE, even if it's API-compatible, even if it's literally exactly VSCode recompiled with another name.
And it's yet another thing to proactively insert checks for that.
How is it not open-source? It's licensed under MIT + VS Marketplace Terms: https://github.com/microsoft/vscode-cpptools?tab=License-1-o... If you fork it and don't use VS Marketplace, it's only MIT. Or am I missing something?
You missed that the ‚binary‘ vsix file has a different license: https://marketplace.visualstudio.com/items/ms-vscode.cpptool... (The license like that existed before cursor, it was basically the reason for vscodium) (Source is https://marketplace.visualstudio.com/items?itemName=ms-vscod... the license link at the bottom) The same problem with the c# extension, which has had an even bigger shitstorm since some parts o…
Earlier quoted context omitted.
Eh, I mean it's a fork. They can keep updating their fork forever. Reality is they want complete control over the product, and VS Code doesn't expose everything in the extension API.
Sure, but they depend on a bunch of Microsoft proprietary extensions (that they can't fork) that ban usage in VSCode forks, and they knew this when they made the choice. This was an inevitable outcome from Microsoft's side. I'm sure they want to remain in business more than they want complete control over the product.
Microsoft still holds the crown when it comes to C# debugging, but for most proprietary MS extensions there are free, open source alternatives. They may not be as polished as the ones Microsoft actually pays people to maintain, but I don't see why Cursor would actually depend on any of the proprietary ones if you're not using it for C# dev (and even there competitors like Jetbrains have figured out a way to make it work).
To be clear, I'm don't like the Microsoft has a proprietary Marketplace, but a company openly violating the terms of use for their own profit is a bit much in my opinion. > Cursor allegedly has been flouting Microsoft terms-of-service rules for some time now by setting up a reverse proxy to mask its network requests to the endpoints used by the Microsoft Visual Studio Marketplace. This allows Cursor users to install…
cursor also hijacks the 'code' alias to start vscode from the cli, which I use a lot. It's extremely annoying to have cursor start instead and unnncessarily difficult to get rid of. I removed cursor because of this.
I don't understand the problem. It sounds like the C/C++ extension was proprietary. This sort of thing can always happen when you rely on proprietary software. Make an open source C/C++ extension and you wouldn't have this problem.
The extension itself it MIT licensed (so could be hosted on the open VSIX store, if it wasn't down because the Eclipse project is suffering from server issues right now). In theory any fork can patch out the check and re-release the extension.
However, the extension packages some binaries that are proprietary, and have been since about four years ago. People could re-implement those and re-release an open version of the extension, but you can't just (legally) take the proprietary binaries and ship them if you don't have the license.
Open alternatives actually exist, but their quality and ease of configuration depends on your use case. In large projects the proprietary extension seems to be worse from what I've read.
I don't understand the problem. It sounds like the C/C++ extension was proprietary. This sort of thing can always happen when you rely on proprietary software. Make an open source C/C++ extension and you wouldn't have this problem.
Yes, that is what I thought, too. (It would be a good idea to have a open source C/C++ extension anyways, whether or not the proprietary extension stops working with non-Microsoft code.) (Maybe there is such extension; I don't know; I don't use VS Code and VS Codium etc.)