Why is Rider so bad?

Seriously... howcome you are able to make such nice addons, and yet your IDE for C# is so bad.

Rider suffers from frequent crashes and the solution explorer's inability to refresh such that one **has** to restart the IDE in order for the changes to take effect, is detrimental to the overall productivity.

Please fix this.

 

**Edit:** removed the ranting - made it more constructive.

4 comments
Comment actions Permalink

What do you find to be bad? I've been using Rider professionally for ~7 months without any issue.

In fact, I much prefer it to Visual Studio.

0
Comment actions Permalink

For starters, the frequent crashes or solution explorer's inability to refresh such that one **has** to restart the IDE in order for the changes to take effect.

I apologize for the ranting in the previous post, but I just expect more from JetBrains, considering they normally make such nice tools and add-ons.

By comparison Rider is much like Eclipse, and not Visual Studio.

 

 

1
Comment actions Permalink

The Rider is not bad and I am using it too, no crashes but it is clunky because it is running on Java, All Java applications are clunky and look not so nice comparing with native windows apps. Visual Studio GUI looks much better.

0
Comment actions Permalink

Jetbrain rider has so far proved useless for me as code beginner. One the Intellisense or should be called Autocomplete (Intellisense does not exist as a setting) isn't available on start up so stupid. JetRider should have a startup choices of new to Jetrider and code beginner which cuts out the useless options. I have fight Jetrider to do things. It is not helpful. I already have a probable Jetrider bug of  Instantiation should come with the code form for Unity- instead I have to search for it myself. Jetrider should debug and clean up modes separate- debug just helping you make code and cleanup to improve it. First list on tutorial is unused class- ridiculous waste of initial coding time. 

0

Please sign in to leave a comment.