David Driscoll
@david_dotnet
Web & .NET Developer, Microsoft MVP, Father (of 3 oh my!), Husband, work-a-holic. I work on OmniSharp (http://omnisharp.net) and OmniSharp for Atom Editor
Potrebbero piacerti
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.
“Rape doesn’t exist” “No contraception has ever failed” “No man has ever lied” These people can fuck all the way off.
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).
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?
This is the most I've used twitter since the pandemic started...
Turns out it wasn't so tricky implementing my own language server, thanks to people like @david_dotnet and @bjorkstromm!
We listen and learn. Hot Reload is back in the #dotnet CLI. devblogs.microsoft.com/dotnet/net-hot…
I am rooting for the folks on the .NET team.
The irony of the .NET team yanking hot reload is that is doesn't actually work for me in VS2022, only works (worked?) via dotnet watch.
Take Developer Ecosystem Survey by JetBrains surveys.jetbrains.com/s3/developer-e…
I've been creating a tool but now contemplating of even releasing due to limitations. You draw a 2D sprite, set the depth of each 'pixel' and presto a 3D model! Since you're working on 1 axis you can probably guess the limitations. Would love to hear your ideas? #gamedev
.NET 6.0 nightly builds for Apple M1 are now available. Works but your YMMV. Please file bugs. Look for "macOS Arm64" @ github.com/dotnet/install…
United States Tendenze
- 1. Lakers 68K posts
- 2. Luka 51K posts
- 3. Marcus Smart 6,651 posts
- 4. Rockets 56.2K posts
- 5. #DWTS 44.8K posts
- 6. Shai 31.2K posts
- 7. Sengun 23K posts
- 8. Double OT 5,696 posts
- 9. Ayton 9,487 posts
- 10. Reed Sheppard 5,831 posts
- 11. Warriors 78.4K posts
- 12. Draymond 6,223 posts
- 13. Kevin Durant 23.3K posts
- 14. Chris Webber 1,682 posts
- 15. Chet 17.4K posts
- 16. Kuminga 6,584 posts
- 17. Caruso 5,144 posts
- 18. #LakeShow 5,613 posts
- 19. Elaine 21K posts
- 20. Curry 29.9K posts
Potrebbero piacerti
-
Glenn von Breadmeister
@condrong -
David Kean
@davkean -
Billy Hollis
@billyhollis -
Julien Couvreur
@jcouv -
Isaac Abraham
@isaac_abraham -
Rodney Littles II
@rlittlesii -
Shayne Boyer
@spboyer -
Scott Addie
@Scott_Addie -
Agnès ZITTE
@AgnesZitte -
Eirik Tsarpalis
@eiriktsarpalis -
Kristian Hellang
@khellang -
Josh Free
@imjoshfree -
Matt Ellis
@citizenmatt -
Anand Gaurav
@adgrv
Something went wrong.
Something went wrong.