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.
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 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.
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.
ICT Architect at a tech services company with 51-200 employees
Real User
Top 10
Nov 19, 2019
* 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)
Desarrollador Java Jr/BPM Jr at Agnostic | a cognitive company
Real User
Jan 27, 2019
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.
At JetBrains, code is our passion. For over 15 years we have strived to make the strongest, most effective developer tools on earth. By automating routine checks and corrections, our tools speed up production, freeing developers to grow, discover and create.
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.
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 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.
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.
* 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 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.