CLion vs PyCharm

CLion is best suited for day to day IDE for C and c++ programming projects. It integrates inbuilt support for GNU Compiler Collection (gcc) and works like a breeze on linux and *nix based platforms. While using this CLion IDE for different versions of projects, we faced a little difficulty to compare the differences of two versions of same file. This could be taken care of in next versions.

It's easy to create virtual environments and install packages for different projects as we may need project-specific packages for doing our experiments, also it's easy to see what changes we have made and create pull requests faster. But sometimes we want some light python editor like Jupiter notebook as PyCharm is relatively heavier, also Jupiter notebooks are a good option when we need to run remote code on local machines.

• User-friendly UI
• Supports VIM for fast coding
• Smart code completion
• Cross-platform support
• Split-windows feature
• Supports both C and C++
• Provides free student license

• Git integration is really essential as it allows anyone to visually see the local and remote changes, compare revisions without the need for complex commands.
• Complex debugging tools are basked into the IDE. Controls like break on exception are sometimes very helpful to identify errors quickly.
• Multiple runtimes - Python, Flask, Django, Docker are native the to IDE. This makes development and debugging and even more seamless.
• Integrates with Jupyter and Markdown files as well. Side by side rendering and editing makes it simple to develop such files.

• Support for SoC from Nordic Semiconductor is not the best on the market.
• It lacks CMake migration tool for older Make projects.

• The biggest complaint I have about PyCharm is that it can use a lot of RAM which slows down the computer / IDE. I use the paid version, and have otherwise found nothing to complain about the interface, utility, and capabilities.

It has the features that I need for my coding

It's perfect for our needs, cuts development time, is really helpful for newbies to understand projects structure

CLion does everything I ask it to do. For me, Unreal Engine 4 compatibility was essential and Epic Game and JetBrains delivered a solid alternative to spending a huge amount of money on the "standard" IDE for game development on Windows. The user interface is sharp and modern without all of the silly frills many software suites now employ. It integrates well with source control systems we use and also works well, as expected, with other JetBrains development tools and assistants.

I am giving it a 9 out of 10 because I did not even need official support from the CLion team but rather, every time I came across a problem, I have been able to solve it within the community itself. This is so precious that you don't even need the help of the program's development/support team. There's a huge community of users that backs you up.

I rate 10/10 because I have never needed a direct customer support from the JetBrains so far. Whenever and for whatever kind of problems I came across, I have been able to resolve it within the internet community, simply by Googling because turns out most of the time, it was me who lacked the proper information to use the IDE or simply make the proper configuration. I have never came across a bug in PyCharm either so it deserves 10/10 for overall support

CLion is at par when compared with many established IDEs. With lesser cost in owning this IDE to the ease of use of this IDE it can be very well chosen and opted for the main IDE with in your organization. Its plugin add on capabilities will surely help to integrate other compilers of other programming languages.

PyCharm is the best IDE for python development. PyCharm offers various features: source code completion, support for unit testing, integration with Docker/GitLab/Git, ability to manage and configure virtual environments, auto-indentation, and re-factoring code with ease. Support for JSON/Shell scripts and support for Flask/Django Other tools are effective for creating isolated scripts but not for handling projects with more than two scripts.

• Greatly decreased initial time needed by a new employee to start coding.
• Refactoring features allowed to reduce the technical debt in majority of our projects.

• Buying the licensed pro version is a bit costly, but overall because of its features and its speed, the time taken by a developer to develop something can be improved. Indirectly getting a good return of Investment.
• Considering the team size and its features, one can go for the licensed version as the ROI is high.
• Customer support is also good for a licensed version, thereby saving the time, which in turn shows ROI as high.