News for hackers. Stuff that matters.
Re:.NET Core 3.0 by gtsteve on Monday September 23, 2019 @01:54PM (#21051492)
VS is very good but I've been using Rider since the start of this year for most work, I found it to be a very strong competitor.
Re:.NET Core 3.0 by DavidWoof on Monday September 23, 2019 @03:09PM (#21052421)
I've been Rider almost exclusively for about 2 years now, ever since I've been coding Core. VS is fine, but VS w/Resharper is a dog. With Rider, R# is a first class citizen, which makes a huge difference. Not to mention that the vim emulation and other addons are solid due to being shared with the intellij suite of apps.
Re:.NET Core 3.0 by equasar on Monday September 23, 2019 @05:39PM (#21054006)
VS 2019 has been integrating lots of new refactorings that were only on R#. It appears that they are more and more between small releases.

I'm happy to never need to use R# anymore.

Re:.NET Core 3.0 by redhale on Monday September 23, 2019 @07:12PM (#21054769)
Refactorings are but one feature of Resharper. The code hints/suggestions are still far better than vanilla VS, unfortunately (imo).
Re:.NET Core 3.0 by TurboHaskal on Monday September 23, 2019 @04:02PM (#21052973)
Rider blows Visual Studio out of the water for anything F# as well. It is really a shame that Microsoft no longer seems to care about it.
Re:.NET Core 3.0 by GordonS on Wednesday September 25, 2019 @05:53AM (#21069226)
I switched to Rider from VS with R# after growing weary of the frequent pauses and the constant whining of my laptop fans.

It took a while to configure the colour scheme to something I was comfortable with, but otherwise the experience has been really positive - I love it!

Re:.NET Core 3.0 by hizanberg on Monday September 23, 2019 @03:16PM (#21052494)
Same, I’ve been using Rider whenever I can, VS only when I have to. Much better IDE overall.
Re:.NET Core 3.0 by LandR on Monday September 23, 2019 @02:16PM (#21051772)
Visual studio crashes and hangs on me multiple times a day. Rider is just solid.
Re:.NET Core 3.0 by metamet on Monday September 23, 2019 @02:27PM (#21051904)
Visual Studio does this for me a lot as well, especially when projects become larger. The number of times the typeahead caused the app to hang is too numerous to count.

Part of me misses .NET, but I've been mostly working with Golang and Node lately. Visual Studio Code is pretty stellar. Maybe someday VS will catch up to VSC. :)

Re:.NET Core 3.0 by jsingleton on Monday September 23, 2019 @02:52PM (#21052216)
I also have problems with VS resource usage. It appears to depend on what file type the focussed tab has open. It's still 32-bit, which can't help.

Never had perf issues with VSC, which is surprising considering it's web tech. It's a different class of app to VS but much nicer to use, and of course it's cross platform.

Re:.NET Core 3.0 by mumblemumble on Monday September 23, 2019 @02:55PM (#21052248)
I haven't used VS in about 2 years now, so this experience may be too many versions out of date to be relevant anymore, but for a while I had very similar problems. And then I uninstalled ReSharper, and VS all of a sudden became very snappy.
Re:.NET Core 3.0 by ToFab123 on Monday September 23, 2019 @11:43PM (#21056291)
You can get most of snappiness back even with ReSharper installed. If you dig into the ReSharper option menu, under "Product and feature", and untick everything in the feature section except "Navigation and search", you still get the amazing refactoring and writing-code support but without your computer slows to crawl speed.
Re:.NET Core 3.0 by Nuzzerino on Monday September 23, 2019 @02:55PM (#21052244)
I try to avoid anything by Jetbrains, as the process of reporting bugs and trying to get show-stopping bugs fixed has been a nightmare with them. This was during their RC phase of Rider, where I had a number of bugs. They went ahead and shipped it to full release (where it was no longer free of charge) without fixing a single one of the bugs I reported and even followed up on. What is the point of an RC beta test if you are so behind on bug fixes that you're not even able to triage all incoming reports? Seems like it should still be called beta at that point.

To their credit, I've had great experiences with RubyMine, but that was the exception to the rule for my experiences with Jetbrains IDEs.

Edit: Before anyone else downvotes, I'll point out that I realize this is not the experience others have had, but I was not exaggerating these claims.

Re:.NET Core 3.0 by mythz on Monday September 23, 2019 @03:21PM (#21052547)
That’s about the opposite experience that I’ve had, they’ve always been quick to respond and resolve my reported issues, they’ve even created tickets themselves when I’ve reported them over Twitter.
Re:.NET Core 3.0 by Nuzzerino on Monday September 23, 2019 @04:05PM (#21053000)
This bug has been open for 3 years (and not touched for 2 years). It's stuff like this you see everywhere: https://youtrack.jetbrains.com/issue/RIDER-3461
Re:.NET Core 3.0 by james_s_tayler on Tuesday September 24, 2019 @08:41AM (#21059443)
Our team uses Rider at work. We love it. The UX blows VS out of the water. Nice and fast too. Unit tests are a first class citizen in Rider too.