Tech specs
1-2 of 2 reviews
What is our primary use case? 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. How has it helped my organization? 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. What is most valuable? 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. What needs improvement? 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. For how long have I used the solution? I've used the solution for two years. Which solution did I use previously and why did I switch? We previously used Visual Studio Enterprise 2022. What's my experience with pricing, setup cost, and licensing? 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. Which other solutions did I evaluate? We also evaluated Visual Studio Comunity, Visual Studio Code, and Mono Development. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
What is our primary use case? 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. How has it helped my organization? 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. What is most valuable? * 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. What needs improvement? * 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) For how long have I used the solution? I have been using JetBrains for three years. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
