Huh, just the other day i was talking about how JetBrains products succeed in being some of the best IDEs around, but fail at the use case of just wanting to edit text files, where Notepad++, Visual Studio Code, Emacs, Sublime and vim could all be preferable to it: https://news.ycombinator.com/item?id=29362960 And then JetBrains come out with this... That's certainly pleasant to see!
thats funny I've always found jetbrains IDE to be error ridden annoyances where I end up spending more time dealing with problems the IDE has caused than developing software.
My personal experience has been pretty much the opposite of this, as someone that uses Java almost every day and other languages occasionally (.NET, Python, PHP, Ruby, JS/TS, SQL, a little bit of Go).
If i had to rank all of the IDEs that i've used from the most productive/stable to the least, it'd go about like this:
- IntelliJ IDEA: the best way to write Java, and the best of JetBrains' products, period
- most other JetBrains IDEs: Rider (a bit slow, but a lot of good features), PyCharm (slow to start, but nice to use), PhpStorm (no complaints, it's just that Laravel refactoring is way behind what Java gives you), RubyMine (one of the better options for Rails, despite its dynamic nature, autocomplete just works), WebStorm (a pretty good way to write JS/TS, even with some outdated and obscure codebases, like ES5 with AngularJS and no webpack), DataGrip (a bit niche since other IDEs cover a lot of the other functionality, but also present in the ecosystem), Goland (just recently started using, similarly usable); all of those are definitely worth the Ultimate subscription of their products IMO
- Visual Studio: a pretty good IDE that has a similarly slow startup to Rider but feels good afterwards, especially for developing against Windows and doing .NET, perhaps better than Rider in some regards, though i hate the VS Installer with a passion, still haven't removed all of the crap it installed, years later, and the checkboxes for the features you may/may not want are confusing and it's a massive waste of space (though i guess the Python etc. integrations are nice for some + Azure stuff); also has the most tutorials for it out there
- NetBeans: my darling a few years ago, completely free, reasonably capable and has some other tooling based on it (e.g. jMonkeyEngine SDK), if it had better framework integration and wasn't so dead, i'd gladly keep using it, since the keybindings are perhaps some of the most sane i've ever seen; also supports PHP and C/C++, but those are a bit weaker here; also really slows down with large projects
- Eclipse: i hate Eclipse, some people swear by its workflows, but i've used plenty of horrible software that decided to use it as a platform and did so poorly (4EM tools, model driven development tools for generating source code, some random remote'ish development platforms) though it's also really poor on its own, as a regular Java IDE; unhelpful, inconsistent and slow
- Android Studio: perhaps one of the few tools that are worse than Eclipse (aside from obscure SWI-Prolog IDEs and some ASM IDEs), i don't know what went so wrong here, but it's slow, chugs memory, makes the CPU hit 100% usage with 4 cores and just generally feels like a bad solution, i'm not sure where JetBrains went wrong, but since last trying it about 3-4 years ago, i haven't picked it back up since
That's about it, each IDE has its advantages and disadvantages.
For example, even IntelliJ might need you to dig through the VM and memory options when you want to open projects that approach 1M SLoC, since the defaults might not be good enough.
Oh, and in regards to DB tools, MySQL Workbench would have the #1 spot (since the modelling and forward/backward engineering and schema sync functionality is to die for, when planning things), DataGrip the #2, pgAdmin the 3# (the UI just feels non-native and bad, cumbersome to use, unresponsive) and SQL Developer would be near the bottom, after whatever else software i'd decide to list (horrible whenever you try to do anything apart from just writing and executing SQL, e.g. the modelling bits have failed to save and later re-open files pretty consistently).