News for hackers. Stuff that matters.
Re:The Case for C# and .NET by ivraatiems on Monday July 25, 2022 @02:10AM (#32221058)
I've been a .NET developer professionally for seven and a half years. Rider is the way to go. Visual Studio has improved dramatically over the last decade or so, but Rider is still way ahead of it on code search/discovery, performance, and general user experience. I did a tech talk at my company where I demoed Rider vs Visual Studio 2019 performance on our bigger projects... it was embarrassing for VS. VS 2022 was substantially better on performance, but also crashed during the demo.
Re:The Case for C# and .NET by bbkane on Monday July 25, 2022 @05:39AM (#32222312)
I'd love to watch that talk if you're comfortable posting a link
Re:The Case for C# and .NET by ivraatiems on Monday July 25, 2022 @10:27AM (#32224765)
Unfortunately, because it contains proprietary source, I cannot :(.
Re:The Case for C# and .NET by nonbirithm on Monday July 25, 2022 @08:47PM (#32232943)
I'd love to use Rider on Linux or even Windows. Sadly the lack of .NET hot reload on Linux and Rider's issues with hot reload on Windows are what keep me on Visual Studio. (Rider's implementation of hot reload doesn't support assemblies loaded at runtime yet, which my application depends on).

It's sad that the time saved with Visual Studio's hot reload alone seems to outweigh the (massive) performance gains from using Rider, given that I have to restart VS from its memory leaks multiple times a day or it will slow to a crawl. Omnisharp isn't performant or reliable enough for daily use, either. The current state of .NET tooling leaves me unsatisfied.

Re:The Case for C# and .NET by GiorgioG on Monday July 25, 2022 @10:30PM (#32233582)
I’m amazed hot reload works consistently enough for you to be able to use it.
Re:The Case for C# and .NET by the_only_law on Monday July 25, 2022 @08:30AM (#32223408)
Visual Studio is great, but also one of the most broken bits of software I've had to use.
Re:The Case for C# and .NET by 202206241203 on Monday July 25, 2022 @08:06AM (#32223219)
Rider does not have a community edition unlike IDEA. It was created due to a combined threat of VS Code and Roslyn and is the reason ReSharper is almost neglected these days.
Re:The Case for C# and .NET by ziml77 on Monday July 25, 2022 @09:03AM (#32223686)
ReSharper isn't a heavy focus because it's not worth it anymore. To get the same performance as other tools they'd need to throw out a ton of work and rewrite it for Roslyn. With Rider, they get to continue to use their existing ReSharper codebase to power it.
Re:The Case for C# and .NET by 202206241203 on Monday July 25, 2022 @09:10AM (#32223752)
They don't forget to charge same (even increased) fee for minimal updates, though.
Re:The Case for C# and .NET by WorldMaker on Monday July 25, 2022 @03:51PM (#32230023)
Was that comparison both with or without ReSharper? Were you comparing fresh installs with no plugins on both sides?
Re:The Case for C# and .NET by aaaaaaaaata on Monday July 25, 2022 @07:49AM (#32223099)
And...how do both companies compare in what telemetry they're sucking out of devs?
Re:The Case for C# and .NET by SamuelAdams on Monday July 25, 2022 @09:06AM (#32223713)
Fair question, devs who do not want to share telemetry for the dotnet core SDK simply need to set an environment variable. VSCode has a similar setting in the options. Not sure about Visual Studio as I haven’t used it in a while.

https://docs.microsoft.com/en-us/dotnet/core/tools/telemetry

Re:The Case for C# and .NET by fartcannon on Monday July 25, 2022 @09:30AM (#32223973)
Opt out is ridiculous for a programming language. Do you really want to play security whack-a-mole with your development environment?

There are countless, better privacy respecting tools.