sdk VS vscodium

I opened an issue since I couldn't find docs that indicate what they were working on to improve the start time, and they replied:

https://github.com/dotnet/sdk/issues/49197

It's not about being "cool"

It's about the motives

"it's open source"

"it now works on linux"

it all doesn't matter if they'll go after your ass if you dare build tooling with their debugger (jetbrains)

of when they want to remove a feature overnight to make it exclusive to visual studio windows

https://github.com/dotnet/sdk/issues/22247

it's this kind of things that makes it hard to recommend to people, and Microsoft can't be trusted

I hate to defend telemetry of all things but in this particular case the criticism is unfounded and lacks context:

https://dotnet.microsoft.com/en-us/platform/telemetry

https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr...

https://github.com/dotnet/sdk/tree/main/src/Cli/dotnet/Telem...

In any case, Debian would use https://github.com/dotnet/source-build and dotnet/dotnet, and could easily include the argument or a patch for this. It’s unlikely to be an issue. My bet it was not in Debian because there was no one to take initiative or there was but that person has faced a backlash by people in Debian who are similar to vocal minority here that posts FUD because of their little personal crusade.

FWIW telemetry can be easily opted-out, which the SDK explicitly tells you about, and there is a page that has full list of the kind of data that is collected (usage metrics and tooling crash stack traces). You can also review the metrics yourself.

About: https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr...

Collected statistics: https://dotnet.microsoft.com/en-us/platform/telemetry

Source code: https://github.com/dotnet/sdk/tree/main/src/Cli/dotnet/Telem...

In either case, many CIs simply have 'DOTNET_CLI_TELEMETRY_OPTOUT=' and call it a day.

They used to gather all command line arguments until they later decided that (oops!) it's "not acceptable per our privacy policies"[0] and they really shouldn't have been doing that. They have also had issues with anonymization not being implemented properly, the opt-out mechanism not working in some edge cases, forgetting to even tell users about the need to opt out, and who knows what else.

Also, monetary value is not the only reason you might want to keep information private.

[0] https://github.com/dotnet/sdk/issues/6145#issuecomment-22010...

[DllImport("libc")] private static extern uint geteuid(); public bool IsCurrentProcessElevated() { if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows)) { // https://github.com/dotnet/sdk/blob/v6.0.100/src/Cli/dotnet/Installer/Windows/WindowsUtils.cs#L38 using var identity = WindowsIdentity.GetCurrent(); var principal = new WindowsPrincipal(identity); return principal.IsInRole(WindowsBuiltInRole.Administrator); } // https://github.com/dotnet/maintenance-packages/blob/62823150914410d43a3fd9de246d882f2a21d5ef/src/Common/tests/TestUtilities/System/PlatformDetection.Unix.cs#L58 // 0 is the ID of the root user return geteuid() == 0; }

> There's definitely things they tried to improve on that... weren't really improvements. The way "assemblies" are matched in .NET is much more sophisticated- the goal there was to try to kill DLL hell. It evolved into the Global Assembly Cache, which is sort of the Windows Registry of DLLs. Not a huge fan of those bits.

The Global Assembly Cache did not make the jump to the modern .NET (Core). There was the thing called `dotnet store`, but it’s broken since .NET 6: https://github.com/dotnet/sdk/issues/24752

The assembly redirection hell has also been greatly reduced there.

I do the same.

I have a small write-up here: https://chrlschn.dev/blog/2023/10/end-to-end-type-safety-wit...

You get end-to-end type safety (even better once you connect it to EF Core since you get it all ways to your DB).

With this setup with hot-reload (currently broken in .NET 8 [0]), productivity is really, really good. Like tRPC but with one of the most powerful ORMs out there right now.

[0] https://github.com/dotnet/sdk/issues/36918

Noticed an open issue just now.

You're thinking of https://github.com/dotnet/sdk/issues/22247

Visual Studio Code is distributed under the MIT license, a permissive license that allows you to do anything with the source code. This license is recognised by the OSI as an Open Source license. And quite predictably, a few forks of VSCode exists. VSCodium seems to be the most popular.

Thanks, haven't tried it yet, but just found the relevant configuration settings described in the docs [0] and more detail on Stack Overflow [1].

[0] https://github.com/VSCodium/vscodium/blob/master/prepare_vsc...

[1] https://stackoverflow.com/questions/44057402/using-extension...

A 1st party ad is still an ad, though in isolation I do I agree that it's quite mild all considered. With context however (this being Microsoft's doing, and all the AI/Adware/telemetry/darkpatterns they're cramming into everything), I share OP's derision for this development in a tool that has become a centerpiece for many developers workflows, dev environments, and ancillary (plugins) ecosystems.

Thankfully, for now at least, VSCode is MIT Licensed [0], source available [1], and if built from source it does not include CoPilot, Telemetry or MS' other crapware or branding. VS Codium [2] compiles this source for you without the cruft and makes those binaries/installers available [3] if like.

For those that like CoPilot, VSCodium even has a guide on how to add it to VSCodium/Source Built VSCode [4]

0: https://github.com/microsoft/vscode/blob/main/LICENSE.txt

1: https://github.com/microsoft/vscode

2: https://vscodium.com/#why

3: https://github.com/VSCodium/vscodium/releases

4: https://github.com/VSCodium/vscodium/discussions/1487

Notably absent are all of the remote debugging extensions and Copilot. This would be a deal-breaker for many.

[0] https://github.com/VSCodium/vscodium/blob/master/docs/index....

Thanks, good spot.

So Mozilla, an organisation that commends itself for working to put control of the internet back in the hands of the people using it, [0] is creating a situation where the FOSS community needs to maintain its own 'cleansed' builds, akin to VS Code/VS Codium [1] and, to a lesser extent, Chrome/Chromium. [2] (The Chromium case is somewhat different; Google maintains both the FOSS Chromium builds and the non-Free Chrome builds).

4 years ago I commented that It's just non-stop with Mozilla, isn't it? They have the curious pairing of technical excellence, and a long history of awful non-technical decision-making. Little seems to have changed. [3]

[0] https://www.mozilla.org/en-GB/about/

[1] https://vscodium.com/

[2] https://en.wikipedia.org/wiki/Chromium_(web_browser)

[3] https://news.ycombinator.com/item?id=26873740

I've been running vscodium for a couple of years now, and they rip out the MS specific stuff so no ChatGPT and so forth. I haven't noticed any slowdowns.

Maybe give it a try? https://vscodium.com/