211–220 of 227 posts
It's felt for a long time to me that MS has been slowly boiling the frog with VSCode - injecting little bits of proprietary/non open source functionality at a time. I want to switch to something else but the community at large for the languages I develop in is pretty centered on VS code (Rust and Typescript mostly), and it's a really good editor. Obviously not helped by Typescript being stewarded by MS too.
VSCodium is VSCode without the Microsoft EULA and extra stuff. Most extensions are available in the app, others through openvsx.org
I'm worried that Microsoft is succeeding at making the semi-proprietary version of VSCode the only viable option, while keeping the OSS forks as second-class citizens at best.
Earlier quoted context omitted.
It’s possible to do both of those and still not trust MS. I don’t believe that vscode will be this free mostly open editor forever. I’m expecting to see vscode pro or something any day. Typescript can, very cynically, be seen as an on-ramp for vscode, as vscode has pretty much the best typescript suppor.
Luckily that’s why we have OSS licenses, if/when they do that there will be a community fork.
One would hope, but if all the project’s experts are hired and have been working for a company that closed their once open source project, forks will have a hard time surviving.
That’s why redis and elastic search didn’t see an explosion of popular forks. Terraform has opentofu, but I haven’t looked in on them in a while.
I don’t believe there are any Atom forks around since Microsoft killed that project after aquiring GitHub.
Also, the actual Visual Studio code you download from their website is NOT fully open source. It contains closed source extensions and configurations.
Earlier quoted context omitted.
That just tells you where in the EEE lifecycle you are. Embrace, extend, and extinguish `---> https://en.wikipedia.org/wiki/Embrace%2C_extend%2C_and_extin...
Embracing, extending, and extinguishing their own tool? Please consider what you are going to say before you say it.
Consider how C# support in VSCode got nerfed recently:
https://news.ycombinator.com/item?id=31760684
https://github.com/dotnet/vscode-csharp/issues/5276
There was another event only a few months ago, but I can't find the reference.
Earlier quoted context omitted.
> Visual studio is open source Sort of. The core is, and the installable binaries with telemetry and properietary extensions are not. The open source, telemetry-free version of VSCode is called VSCodium: https://vscodium.com/ > Didn't cusor fork it and is building it features directly into the fork? Yes, in their recent interview with Lex Fridman they argued that life as an extension is too limiting. The main reason…
> The open source, telemetry-free version of VSCode is called VSCodium The open source, telemetry-free version of VSCode is called VSCode. The VSCodium people simply build it for you and package it for you.
If you choose to drive it, it's full price.
Earlier quoted context omitted.
VSCodium is VSCode without the Microsoft EULA and extra stuff. Most extensions are available in the app, others through openvsx.org
Compatibility can be iffy though. I eventually switched back to the official VSCode application because I was fed up that extensions kept breaking randomly. I'm worried that Microsoft is succeeding at making the semi-proprietary version of VSCode the only viable option, while keeping the OSS forks as second-class citizens at best.
Earlier quoted context omitted.
What is this Cmd+K / Composer experience? For me Cmd+K is the first hotkey in the multi-key bindings that I believe ship by default. Searching for Composer just suggests the PHP Composer extension that I assume isn't what you mean.
search cursor composer
I'm starting to check this out now: https://cursor.directory/learn
It's felt for a long time to me that MS has been slowly boiling the frog with VSCode - injecting little bits of proprietary/non open source functionality at a time. I want to switch to something else but the community at large for the languages I develop in is pretty centered on VS code (Rust and Typescript mostly), and it's a really good editor. Obviously not helped by Typescript being stewarded by MS too.
Everyone is reading this as intentional anti-competitive practices. While that may be true, isn't another reasonable explanation that the Copilot development team is moving as fast as they can and these sorts of workarounds are being forced through in the name of team velocity? It takes a lot more time/energy to push public APIs and it's probably a very different team than the team developing the copilot extension. S…