JetBrains IDEs Reviews

I use JetBrains IDEs and Visual Studio in tandem. Within JetBrains IDEs, I use IntelliJ. IntelliJ and Visual Studio are what I use primarily.

Developing code and writing code is the key use case for IntelliJ.

For me, the UI is what stands out. I do not know if it is not that appreciated, but the UI for IntelliJ works well for me. Because I have been using it for a very long time, I am comfortable using IntelliJ and have not switched to other solutions. I primarily write Java code, which is why IntelliJ works best for me. When I need to switch to something like Python for another purpose, that is when I use Visual Studio. I have not explored the new solutions that have come out from OpenAI yet. These two tools are what I am more comfortable with, which is why I continue to use them.

I am using the code completion feature in IntelliJ, and it helps me with my development processes.

I use advanced debugging tools.

The advanced debugging tools are useful for resolving code issues.

The integration with version controls is seamless. GitHub is what I use. For my professional role, I need to use GitHub Enterprise, and the way it is set up in my enterprise, it does not allow linking it with IntelliJ. That is where I am stuck using the CLI. GitHub itself has a very robust CLI, so I have no complaints there. For personal use, GitHub integrates really well with IntelliJ.

The UI is pretty good and very intuitive. I actually use the new UI which IntelliJ provides, and that is very intuitive and good.

I have used solutions such as GitHub code scanning, WatchTower, and Dependabot, but I do not regularly use them. I have used Dependabot, but I do not regularly use it.

I have been working with IntelliJ since the time I was pursuing my bachelor's degree, which would be seven or eight years of using IntelliJ.

I have noticed that when I switch to less powerful machines, IntelliJ seems to use up the RAM and the machine gets really slow and really hot quite quickly, which is not the case with Visual Studio. In my opinion, IntelliJ is more heavy on the memory compared to Visual Studio. I do not know whether both can be compared as an apple-to-apple comparison. IntelliJ seems to be pretty heavy. If you are using powerful machines, or if you are on a Mac as I am, you are good and probably will not be affected by the slowness as much.

I would give it a five for scalability, the ability to scale and the ability to expand.

We are not using Checkmarx anymore.

We replaced Checkmarx and started using another ASPM solution.

The initial setup for IntelliJ is pretty simple.

One more thing I may add is that we have Copilot from GitHub in the cloud, and there are other new AI coding assistant tools. I have not explored much on the JetBrains IDEs side. I am not sure whether JetBrains IDEs itself has something proprietary that can do something similar. Especially after Microsoft acquired GitHub, the Copilot integration with Visual Studio is really nice and really helpful, and very seamless. JetBrains IDEs does have an integration with Copilot that you can do. But because Visual Studio is maintained by Microsoft, they do a really good job in the integration and make it much more seamless compared to something IntelliJ.

GitHub is what I am using for version control.

Mostly with GitHub I am working for version control.

One year back was the last time when I worked with Dependabot.

I would absolutely use a plugin for the IDE for open source like maybe Apache or maybe something from JetBrains IDEs.

I would rate IntelliJ a 6.5 for my final mark for the product.

I use JetBrains IDEs for building applications with Python as the backend. I use JetBrains IDEs as my IDE for really everything, including for database management. I connect through my database there, build out all the code for the backend, and use Angular, which works in JetBrains IDEs for my frontends and other different software SDKs that I attach in. That is primarily what I use JetBrains IDEs for.

I really love the database management within JetBrains IDEs, as it is very easy to just connect my database from my IDE, which I find very convenient. The terminal interface within JetBrains IDEs allows me to run a host of different commands that interface with my code. More recently, I have been exploring a model or MCPs, such as connecting to AI, specifically connecting through my code in JetBrains IDEs to OpenAI's APIs to allow ChatGPT to see my data and give me information on that. I do all of that through JetBrains IDEs, and I consider JetBrains IDEs as an orchestrator of all of that.

I do use JetBrains IDEs's intelligent code completion feature, and I appreciate it. It helps me develop faster, and since I obviously will not remember every syntax, it is very helpful for that. That is a great feature.

I would rate the advanced debugging tools in JetBrains IDEs for resolving code issues efficiently as a ten out of ten. It is straightforward for attaching to a process and diving into the code to see where I have an error or if some variable is off, whatever the case may be. It all just works very conveniently.

I have utilized JetBrains IDEs's version control integration quite extensively as it pertains to the packages that are involved.

I have used JetBrains IDEs's Code With Me feature, allowing me to connect with senior developers to get help when needed and to look at code together to pair program live. I have used that a few times.

One thing I think could be improved in JetBrains IDEs is the integration with ChatGPT, which I feel could be deeper. Some of it is a bit sketchy; it would be great to be able to follow the same threads within JetBrains IDEs for deep debugging dealing with whatever I am seeing in ChatGPT, especially for debugging. That would be a nice to have.

I have been working with JetBrains IDEs for about five years now.

I would rate JetBrains IDEs's stability and reliability as a nine out of ten, only because there have been a few times where I needed to reboot the IDE or my computer to get it functional again. I have never had any issue that a reboot did not fix, but I would say seldomly I will see some corruption or strange characters show up in my debugger that I cannot really resolve without a reboot.

I would rate how scalable this solution is as a ten.

I do not often communicate with the technical support of JetBrains IDEs. I have done that every now and then if there is a bug or something that says to send analysis to JetBrains IDEs, but that is very rare.

I would rate the technical support from JetBrains IDEs as a ten.

Regarding a licensing matter, since I use JetBrains IDEs on multiple laptops, I needed to reach out to get some things situated there, and they have always been very responsive and have helped me.

Positive

Before JetBrains IDEs, I used Visual Studio Code quite extensively, but as of now, I do not use that very often since I do not need to.

I participated in the initial setup and deployment of JetBrains IDEs for myself and at work.

There really were no challenges during my setup process. It was mostly just the install and connecting to the repository, so getting up and running in JetBrains IDEs was probably less than thirty minutes.

I feel that I have seen a very profitable return on investment compared to if I tried to use Visual Studio Code or some other IDE or platform. The time that I save by being able to do everything through JetBrains IDEs alone makes it worth the return on investment.

I am aware of the pricing and licensing of JetBrains IDEs, which I believe is around ninety-nine dollars for a year. I find that to be a very reasonable rate.

I did not really evaluate other options or solutions before ending up with JetBrains IDEs. There were some other IDEs and even just doing things using TextEdit for some things and command prompt, but outside of those, I have not.

Being able to query my database directly from within JetBrains IDEs is very helpful in managing data-intensive applications. I am able to essentially update models or metadata within the code, run queries to see the impact on data, and other scripting directly into my database with my stored procedures or scripts. It is all very convenient that I can do all of that in one place.

I do have multiple apps that I am involved with, so I find it very convenient to have multiple apps up at once when needed or easily switch between the different repositories that I have connected.

Starting from an initial concept of an app, such as a hello world app, to a fully enterprise application, I feel that JetBrains IDEs is great because I can just add packages as needed for the management of whatever tool. From the very beginning to the deepest thing I could possibly want to develop, I believe I could do it all using JetBrains IDEs. I would rate this product a ten out of ten overall.

My main use case for JetBrains IDEs is writing code. When I'm doing something that requires specific actions of an IDE, especially debugging and symbol management, I use JetBrains IDEs. For Python, I use PyCharm, and for PHP, I use PHPStorm. I use JetBrains IDEs for writing code and also sometimes for debugging.

The best features offered by JetBrains IDEs include a super attractive set of language-specific tools including debuggers, symbol monitors, and the extensions that come with it. This helps me get a much more in-depth view of my code rather than relying on print or log statements.

The comprehensive debugging suites, including Git integration, database connectors, and SSH connectors, save time and improve code quality.

One of the main issues with JetBrains IDEs is that it is very heavy, taking a lot of time to load and using a lot of memory. A suggestion would be to ask users which features they mainly need and load only those, perhaps implementing a plug-and-play situation with intelligent feature switches.

Pricing is also a concern as it is quite steep for freelancers or individuals in regions such as Sri Lanka.

I have been working in my current field for around two and a half years.

JetBrains IDEs is stable.

JetBrains IDEs works for my requirements, so as far as I'm concerned, its scalability is adequate.

I have used Visual Studio a bit, not a lot, and I mainly switched to JetBrains IDEs because the UI was really awesome. I appreciate minimalistic, cute, and snappy UIs, so JetBrains IDEs checks those boxes.

The main reason I switched from Visual Studio Code to JetBrains IDEs was the UI and the pricing.

Regarding pricing, setup cost, and licensing, I started when I signed up for the student edition with my student ID card back when I was in high school, and I'm still using that.

I do not have a business relationship with JetBrains other than being a customer.

I don't have numbers about the return on investment because I bought it for myself. In my organization, if everyone were to use it, it would save a lot of time.

I personally use the student version and haven't paid anything for it, but I know people who have been using the student version for two or three years in university. I know another person who spent around 1 million rupees to get JetBrains IDEs for five years.

I did not evaluate other options for IDEs as this is my first choice because everyone loves it. Although I explored many more options for a code editor, JetBrains IDEs is the only one I focused on for IDEs.

My advice for others looking into using JetBrains IDEs is that if you can, use the text editor. Plugins can actually get things done, and those are available for other code editors such as Visual Studio Code, Cursor, or Vim. You can use them, and if you can find a free version, go for it. I would rate this product 10 out of 10.

Our main use case is to program APIs in Microsoft Net Core >= 2.2.

The development of APIs under JetBrains Rider allows us to use the Microsoft framework under Linux natively as if we were doing it from Windows.

I never liked Visual Studio Enterprise in any of its versions. I started in Visual Studio Enterprise 2008 and I have seen how the tool has improved over the years. That said, the lack of usability and constant bugs made me dislike that tool version after version.

Jetbrains improved our organization by allowing us to develop Microsoft products on Linux.

The development of APIs in Microsoft Net Core developed under Windows and deployed on Linux machines has an obvious lack of consistency.

Sometimes the behavior of older APIs (Net Core 2.2) is not the same on Windows as on Linux and if the deployment is not done in containers can be different.

In addition, for the control and maintenance of servers, which is much better done under Linux, having the development tool in Linux makes the work easier.

Having the complete development environment in Linux in the same way as in Windows is already the best.

However, the possibility of adding important plugins such as AWS, Azure, Copilot, etc is a necessary option. All of them have a perfect integration and they are regularly updated to the latest version, which is much appreciated.

Particularly, the integration of Vue.js also gives you the possibility to develop frontends at the same time you develop the backend. In this case, Visual Studio Code has a little better integration, however, it is very slight.

One of the most important things to improve is the consumption of resources, mainly memory. You also need a very powerful computer compared to Visual Studio Code or Visual Studio Enterprise.

An important improvement would be the case of having more than one instance open. It is common to have more than one instance because of developing linked microservices or frontend/backend at the same time. Memory usage in this case should be optimized.

The debugging of objects and their manipulation is also not optimal. Sometimes it is difficult to observe variables or very complex objects. There are also memory overflows that sometimes cause debugging to stop.

I've used the solution for two years.

We previously used Visual Studio Enterprise 2022.

The licenses are quite expensive, especially considering that there is a free version of Visual Studio. However, the licenses come down in price as they are rolled out annually, which is a welcome relief.

We also evaluated Visual Studio Comunity, Visual Studio Code, and Mono Development.

It enables us to develop a software that takes configuration Information for services, for servers, for Access Rights, and then generates all IBM MQSC scripts, all documentation (used within SharePoint), and provides a test framework to smoke test all services and queues on proper configuration.

Previously, I used Eclipse. On the recommendation of a colleague, I tried the community edition of IntelliJ 2017. Quickly afterward, I switched to the Ultimate Version. I feel that developing software with IntelliJ is slightly better than Eclipse. With Eclipse, I - from time to time - needed to set up my workspace again; never happened in IntelliJ.

• Fast, and I never had a crash. (Had this in former versions of Eclipse, before I switched).
• Good support for refactoring.
• Good Integration with maven.
• Autocomplete is fine.
• Intuitive usage.
• Easy debugging.
• Many shortcuts.
• Good productivity, at least for me.

• Smaller amount of plugins than within Eclipse; but still then: you get many.
• Sometimes, plugins (from third parties) are not updated.
• Needs a bigger amount of memory.
• For some (good) features, you need to buy the Ultimate Version (for me personally, it was worth the money for myself)

I have been using JetBrains for three years. 

I am using it for a Java Maven project for an important bank located in Argentina. It is integrated into the Git and connected to a Sybase database.

This solution has improved the organization because IntelliJ IDEA has everything integrated into the same tool. It greatly facilitates the learning of use for new developers. Its interface is very good, and besides that, it is very easy to connect to a database, execute stored procedures, create and modify tables, significantly improving time and management.

The most valuable feature that I have found in the tool is the ability to easily connect to the database without problems, interruptions, and errors as they occur in some other well-known tools. Another one that I find valuable is the easiness that the debug mode offers me since it allows you to observe the variables in the route very clearly.

I see as a disadvantage the high prices of the license purchase that is almost $ 500 per year since this limits the use of IDE and especially for those developers who work on their own since it requires a large investment.

Until today the application has not generated an error. Actually, the application is very stable.

No difference is noted for how robust the project is, and it does not affect performance as it grows.

Very good technical support, in addition to its community, it is very broad for troubleshooting and queries.

I have used previous solutions like Java IDE and the features that really made an improvement are the nice interface that it has, the data integrity in the debug mode, and the easy connection and interaction with the database.

The initial configuration was very easy, with having the path/files defined, the rest is very simple.

It was implemented internally by the company.

Although their license cost is high, I recommend it. They will have the satisfaction of using a great and powerful tool, and they will not regret it in the least.

I did not evaluate other options; I just changed it.

It seems to me as one of the best IDEs in the market, they are always releasing new versions with positive improvements, and in my opinion, I recommend it in its entirety.

My main use case for JetBrains IDEs is Java development and technical writing. I have a lot of ongoing open-source projects. I also do a lot of technical writingAzul, which is done in AsciiDoc or in Markdown format, all of which I can do in JetBrains IntelliJ IDE.

The best features JetBrains IDEs offer include the many tools which are available inside the tool and how it makes you a faster Java developer by providing the right tools and code hinting.

Code hinting and the integrated tools in JetBrains IDEs help me with code refactoring, making my code as readable as possible and as efficient as possible. Thanks to the recent AI integrations, I can also generate code which is still readable and can be evaluated and improved very easily.

JetBrains IDEs could be improved with even better integration of AI tools. I would also like it to make it easier to detect new features.

I have been using JetBrains IDEs for definitely over 10 years.

I find JetBrains IDEs mostly stable.

I did not need customer support much, but the few times I did, it was really great.

I previously used a different solution; I used Eclipse, NetBeans, and Visual Studio Code, but there is only one real Java IDE tool and that is JetBrains IntelliJ IDE.

I have not seen metrics, but it is for sure that if you can develop faster with the right tools, the price of the license is won back very easily.

I have no issues at all with pricing, setup cost, and licensing.

Before choosing JetBrains IDEs, I evaluated the ones mentioned previously.

My advice to others looking into using JetBrains IDEs is to definitely do it. I would rate this product an 8.