filipw,
@filipw@mathstodon.xyz avatar

I have spent the past ~7 years helping build the open source OmniSharp, a C# language server, until I retired from the project earlier this year.

For years it provided the backbone for C# experience in Visual Studio Code and other editors and was used by millions of developers. Despite all of its problems, it has to be remembered that it was built in free time by a small group of passionate folks, and building a language experience and providing constant support in this quickly changing landscape is not technically trivial and emotionally very burdening.

From that perspective, I am glad to see that C# developers will finally get a first party language server, supported by the actual MS.NET tooling team https://devblogs.microsoft.com/visualstudio/announcing-csharp-dev-kit-for-visual-studio-code/. What is still not clear to me is licensing - it should be open to all editors and not only VS family of products.

#dotnet #csharp

khalidabuhakmeh,
@khalidabuhakmeh@mastodon.social avatar
arielcostas,

@filipw first of all, thanks for OmniSharp.

Next, I don't understand why Microsoft keeps pushing for Visual Studio licencing and stuff IN VSCODE. AFAIK this new extension(s) are for VSCode, their FOSS editor. Why would they lock features behind the VS "classic" licencing scheme?

TimPurdum,

@arielcostas @filipw I think the reasoning stems from borrowing proprietary code from VS to make the new extensions work. Not saying it's right, just that's what I understood.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • programming
  • DreamBathrooms
  • ngwrru68w68
  • cubers
  • magazineikmin
  • thenastyranch
  • rosin
  • Durango
  • InstantRegret
  • Youngstown
  • slotface
  • khanakhh
  • kavyap
  • mdbf
  • tacticalgear
  • JUstTest
  • osvaldo12
  • tester
  • modclub
  • normalnudes
  • everett
  • GTA5RPClips
  • ethstaker
  • Leos
  • anitta
  • megavids
  • cisconetworking
  • provamag3
  • lostlight
  • All magazines