@secretlabchairs can I get a cat bed addon my chair?!?! My cat loves to sit on the back of my chair but my secret lab one is too skinny for his big booty!!!
The tyranny is that we have allowed Supreme Court justices to be approved with only 50 Senate votes, yet we still allow legislation to require 60. Now with an extremist court that is legislating from the bench, our democracy is at stake: THE FILIBUSTER MUST GO.
@devlead@markrendle@RedHat@shanselman@TylerJewell A few months later I started on https://t.co/WWmdU7B9uW to make a first class lsp library for dotnet. And I’m proud it’s used by the Razor language server, the @Azure bicep server and in a few other places. New version coming next week I hope, just have to finish my unit tests!
@devlead@markrendle@RedHat 2 weeks worth of work and not even a mention about OmniSharp or the team. @shanselman did the demo… yeah I’m a little salty about that tbh @TylerJewell gets his company bought. Anyway that’s sidetracked.
@robmen @philiplaureano @xoofx Neither myself, @filip_woj or @bjorkstromm are employed by Microsoft. I’ve never been approached either to be honest. In the past I thought that it would be cool to work on this stuff every day. I still do, but maybe not for Microsoft.
@markrendle As one who has contributed to it.
I see going LSP as very logical.
My main issue is some community additions to O# likely won't make it to the closed source LSP as they're not prio for Microsoft.
Third-party users of O# i.e. VIM, Sublime just lost a dependency&handed more work
Lot of people complaining that the work Microsoft are doing to bring the C# extension for VS Code up to scratch is not OSS.
Not so many people contributing to the C# extension for VS Code that has been OSS for the last 7 years, which is why it’s not up to scratch already.
MS wants a monopoly on the entire ecosystem, from hardware, tools, CI/CD, cloud hosting, and everything else.
It’s an ominous sign for the future.
It will become untenable for others to operate in this space because MS has an unfair competitive advantage.
My concern with this LSP move isn’t VS Code or OSS values, but what it means for #dotnet as a whole.
It seems that #dotnet and Visual Studio are heading back to being a single product, and everyone not in the VS ecosystem is an afterthought (if lucky).
@jetbrains Why is one provider evil for creating a closed source component in a free open source tool that they've built that's had a massive positive impact on development in general, but another gets away with lots of closed source IDEs?
Along with the whole new MS drama about some closed source component, let's be realistic as well: how many of us will ever look at the code for this LSP component that actually end up using the C# support in @code?