My Experience in Testing JetBrains' IDEs

Chris Wiegman shares his experience testing JetBrains IDEs over a week, ultimately deciding to stick with Visual Studio Code (VSCode). He acknowledges the strengths of JetBrains, particularly in code inspections, where it identified several improvements in his Go projects that other tools missed. The new user interface of JetBrains IDEs is also noted for being modern and less cluttered compared to previous versions. However, Wiegman finds VSCode superior for managing projects across multiple technologies, as it allows him to work seamlessly with Go, PHP, JavaScript, and Rust without needing multiple IDEs. In contrast, using JetBrains required him to install three different IDEs, which complicated his workflow. He also encountered limitations with JetBrains, such as the inability to save files as an administrator, which further reinforced his preference for VSCode. Despite recognizing JetBrains' potential, especially with the upcoming Fleet product, Wiegman feels that for his current polyglot coding needs, VSCode remains the better choice. He concludes that while JetBrains offers powerful tools, the fragmentation of their IDEs does not suit his workflow at this time.

- Chris Wiegman prefers Visual Studio Code over JetBrains IDEs for managing multiple programming languages.

- JetBrains IDEs excel in code inspections, identifying issues that other tools missed.

- The new UI of JetBrains IDEs is modern and user-friendly compared to older versions.

- Using JetBrains required multiple IDEs, complicating Wiegman's workflow.

- Wiegman sees potential in JetBrains' upcoming Fleet product but remains satisfied with VSCode for now.