News for hackers. Stuff that matters.
Re:How Microsoft rewrote its C# compiler in C# and made it o... by alkonaut on Tuesday February 11, 2020 @03:52PM (#22302700)
I had to ditch ReSharper to get to 2019 because together with the performance of the IDE itself, it just wasn't usable. R# ate gigs of Ram and Roslyn does the same. It's not surprising since they basically do the same thing, in managed code! But I can't pay the CPU time and memory to analyze my code TWICE on every edit. I also suspect things like switching build configuration offers thousands of opportunities to have some IDE widget hold references to old compilation data structures which are never garbage collected. On the bright side at least 2019 works pretty well without R#.
Re:How Microsoft rewrote its C# compiler in C# and made it o... by to11mtm on Tuesday February 11, 2020 @04:32PM (#22303115)
> I had to ditch ReSharper to get to 2019 because together with the performance of the IDE itself, it just wasn't usable. R# ate gigs of Ram and Roslyn does the same. It's not surprising since they basically do the same thing, in managed code! But I can't pay the CPU time and memory to analyze my code TWICE on every edit.

I'm holding off on 2019 as much as I can. Between 'forcing' an upgrade for .NET Core 3.0 and the fact Resharper slows it down too much, I decided to give Rider a try.

I'm finding myself not missing VS a whole lot; on one hand Rider is taking way more RAM to start and load, but it stays pretty constant after the first debug session, winds up staying under VS for memory on longer loads (Especially if I've got multiple solutions open) and it's smoother than VS the whole time.

Re:How Microsoft rewrote its C# compiler in C# and made it o... by mycall on Tuesday February 11, 2020 @10:22PM (#22305439)
Is Rider 64-bit?
Re:How Microsoft rewrote its C# compiler in C# and made it o... by ygra on Wednesday February 12, 2020 @04:15AM (#22307236)
It is, but that's not too relevant, as the ReSharper component runs in another process (but that's managed code as well, so probably also runs as a 64-bit process).
Re:How Microsoft rewrote its C# compiler in C# and made it o... by jaked89 on Tuesday February 11, 2020 @04:35PM (#22303140)
I'm not using ReSharper, and never have. The editor simply gets slower every version, and now it's come to the point where I seriously consider downgrading.
Re:How Microsoft rewrote its C# compiler in C# and made it o... by hadrien01 on Tuesday February 11, 2020 @04:30PM (#22303090)
I did the exact opposite: I migrated to Rider, an IDE built around ReSharper. In my experience, it is much faster than VS2019 for my use case (including a huge monolith with hundreds of projects)
Re:How Microsoft rewrote its C# compiler in C# and made it o... by voidwtf on Tuesday February 11, 2020 @06:33PM (#22304145)
I highly suggest giving Rider (also by JetBrains) a try. They run most things in separate processes/threads instead of running everything in the UI thread like VS does. It's almost a drop-in replacement.
Re:How Microsoft rewrote its C# compiler in C# and made it o... by ygra on Wednesday February 12, 2020 @05:01AM (#22307506)
NB: It's not VS that's forcing ReSharper to run in the same process. It's JetBrains refusing to listen to the VS team on how to build VS extensions that need plenty of resources since 2008 ... (they're finally considering it as of summer 2019, I think).