Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
awesome-windows-privacy
A list of awesome tools, documentation and scripts for better privacy on Microsoft Windows
-
omnisharp-vscode
Discontinued Official C# support for Visual Studio Code [Moved to: https://github.com/dotnet/vscode-csharp]
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Some extensions by Microsoft are proprietary (such as their C# debugger and C++ extension) and can only be used with VSCode. For other extensions, you may be able to use them. See the docs at https://github.com/VSCodium/vscodium/blob/master/DOCS.md#ext...
I wonder if MSEdgeRedirect will work around this...
https://github.com/rcmaehl/MSEdgeRedirect
The issue is that it's the way Microsoft conduct business at all. The default should be opt-in not hard to find opt-outs for every patch.
I would say no, there is no way to make it more tolerable unless you run something like shutup10 or https://github.com/TemporalAgent7/awesome-windows-privacy but then again if you care that much you should simply just run Linux because in reality there is no real good solution since spyware is baked right into the product.
The example is not .NET in general, but that specific event when Microsoft reneged on open development tooling[1]. For some people, that was the moment they stopped trusting "new Microsoft" to keep their word (though for me, it was when the Python language server was replaced with a DRM-locked, LSP-noncompliant one[2] a bit before that; unlike .NET hot reload, they didn't backtrack there). I can think the company makes great open .NET tools and at the same time not trust them to close it down on a whim.
Does anyone know where the open xlang reimplementation of MIDL went[3], by the way? (Unlike 1990s MIDL, you can't reimplement this one from the language grammar in the docs, because there is no language grammar in the docs.)
[1] https://dusted.codes/can-we-trust-microsoft-with-open-source and links there
[2] https://github.com/microsoft/pylance-release/issues
[3] https://github.com/microsoft/xlang/pull/529
The example is not .NET in general, but that specific event when Microsoft reneged on open development tooling[1]. For some people, that was the moment they stopped trusting "new Microsoft" to keep their word (though for me, it was when the Python language server was replaced with a DRM-locked, LSP-noncompliant one[2] a bit before that; unlike .NET hot reload, they didn't backtrack there). I can think the company makes great open .NET tools and at the same time not trust them to close it down on a whim.
Does anyone know where the open xlang reimplementation of MIDL went[3], by the way? (Unlike 1990s MIDL, you can't reimplement this one from the language grammar in the docs, because there is no language grammar in the docs.)
[1] https://dusted.codes/can-we-trust-microsoft-with-open-source and links there
[2] https://github.com/microsoft/pylance-release/issues
[3] https://github.com/microsoft/xlang/pull/529
> They did a wonderful job with C# and .NET Core.
And VSCode. One thing all three have in common is that they are all FREE to use--they don't make Microsoft any money directly.
And, for the segment of the developer tools market that wrangles C# code, if VSCode gets too good, it becomes a threat to a cash cow: Visual Studio.
Start here: https://github.com/OmniSharp/omnisharp-vscode/issues/5276#is...
I was surprised to hear this so I went searching. Yep. Wow. [1]
I use GitHub all the time but I never expected it to be mandatory if you wanted to publish a package for a popular open source language.
But as the top says, “If you are interested in helping with this work, please feel free to get started!” (Though only if you’re a contributor or open a duplicate issue)
[1] https://github.com/rust-lang/crates.io/issues/326
I didn't know about https://open-vsx.org/. Very nice! But besides those languages, they are also missing things like the remote ssh extension, which is a big deal breaker for me (and I assume many others regardless of language).
Related posts
- Microsoft eyes partnership with Firefox to make Bing its primary search engine
- How would you get started on a project like this?
- The frist Python library to create cross-platform context menus!
- The frist Python library to create cross-platform context menus!
- Ecossistema .NET em chamas novamente: Microsoft substitui extensão aberta do C# para VS Code por uma versão proprietária