Jira, because it's too slow and bloated from features you never use anyway.
IntelliJ, because it freezes on every 6-7 autosuggestions, on projects of 50-80K LOCs.
They really ought to fire all the PMs who justify their existence by moving menus around.
I've increasing the JVM heap as much as I reasonably could but giving 2GB of Heap to an IDE on a 16GB system seems wasteful.
Hmmm ... one of the things that kind of made me really stick with Gradle is the wrapper tool that make sit dead easy to bootstrap a build without including gradle in the project. Of course, the first thing the bootstrap does is download gradle, so maybe that's what you mean ... but it's been a small price to pay for me.
There are much worse things about gradle ...
What?
Type in the box, click enter?
And I literally hate that for each plugin it looks like it downloads the world. Why aren't plugins just part of the distribution?
Then comes the fallacy: by default, it uses the .m2 folder in your home one. Just because of this, pretty distracted people literally forgets to rebuild all the code, causing breaking or making useless bug reports/complaints on something not available/not compiling/not available at runtime.
Sure, you can do a lot with it, especially in small projects, but the price is just a flawed workflow on big ones. Their release process is the worst UX ever designed
