When comparing IntelliJ IDEA vs Project Rider, the Slant community recommends IntelliJ IDEA for most people. In the question“What are the best IDEs for Android development?” IntelliJ IDEA is ranked 2nd while Project Rider is ranked 5th. The most important reason people chose IntelliJ IDEA is:
IDEA places an emphasis in safe refactoring, offering a [variety of features](https://www.jetbrains.com/idea/features/refactoring.html) to make this possible for a variety of languages. These features include safe delete, type migration and replacing method code duplicates.
Ranked in these QuestionsQuestion Ranking
Pro Smart refactorings
IDEA places an emphasis in safe refactoring, offering a variety of features to make this possible for a variety of languages.
These features include safe delete, type migration and replacing method code duplicates.
Pro Fast and smart contextual assistance
Uses a fast indexing technique to provide contextual hints (auto-completion, available object members, import suggestions).
On-the-fly code analysis to detect errors and propose refactorization.
Pro Android support, JavaEE support, etc
A very complete development environment support.
Pro Lots of plugins
Many plugins are available for almost any task a developer may need to cover. Plugins are developed by Jetbrains themselves or by 3rd parties through the SDK available for writing them.
Pro Stable and robust
IntelliJ IDEA hardly ever crashes or has any issues that plague other Java IDEs like file corruption or slowness.
Pro Support for many languages
IntelliJ supports many languages besides Java, some of these are: golang, Scala, Clojure, Groovy, Bash, etc...
Pro Intuitive and slick UI
IDEA has a clean, intuitive interface with some customization available (such as the Darcula theme).
Pro Clear and detailed documentation
The documentation is exhaustive, easy to navigate, and clearly worded.
Pro Free version available
There is a free community edition (open source) and an ultimate edition, which you can compare here.
The ultimate edition is available for free for one year for students but must be registered through an .edu e-mail account.
Pro Very powerful debugger
With ability to step into a certain part of a large method invocation (Shift+F7), drop frame, executing code snippets, showing method return values, etc.
Pro Many convenient features
These simplify the daily work, e.g. copy/cut a whole line without the need to select it.
Pro New C# IDE based on ReSharper and the IntelliJ platform
ReSharper is a popular Visual Studio Extension for .NET Developers. IntelliJ IDEA is a popular and fully featured JAVA IDE.
Pro Supports all the development lifecycle
Project Rider can build MSBuild and XBuild solutions as well as DNX/.NET CLI projects, and allows debugging .NET and Mono applications. DNX/.NET CLI debugging and CoreCLR support are coming.
Pro Superior "quality of life" features
Extremely good at filling in all the mindless boilerplate type code while you stay productive.
Pro Multiple runtime support
Project Rider supports the .NET Framework and Mono, with CoreCLR support in the works. It also includes templates for creating new projects, and when you create an empty project, it's literally empty
As well as running and debugging multiple runtimes, Project Rider itself runs on multiple platforms. It runs on Windows, Mac OS X, and Linux.
Pro Version control integration
Intellij plugins for Git, Mercurial and TFS plus Local History of files
Pro Decompile code for any .net library
Con Bugs are not solved as often as they should
They are more interested in adding new features or issuing new versions than solving bugs.
Con Built with closed source components
The version with full features is not opensource. Parts of the code are under apache licence though.
Con Slow startup
Startup can be slow deepending on system configuration
Con Cannot open multiple projects in the same window
Con Uses too much RAM
Con Lack of plugins
IntelliJ supports a very small amount of plugins. Althrough thesse are 'quality approved', many features are missing and can't be implemented because of that.
Con Standard hotkeys behave differently
Seems like hotkeys assignment in Idea has no logical consistency.
Like «F3» is usually next match, «Ctrl+W» - close tab, etc — they map to some different action by default.
There is a good effort in making the IDE friendly for immigrants from other products: there are options to use hotkeys from Eclipse, and even emacs. But these mappings are very incomplete. And help pages do not take this remapping into account, rather mentioning the standard hotkeys.
So, people coming from other IDEs/editors are doomed to using mouse and context menus (which are rather big and complex).
Con Relatively young project
Some bugs are to be expected since it's still a relatively young project.