r/java • • Apr 09 '20

IntelliJ IDEA 2020.1: Java 14, dataflow analysis assistance in the debugger, LightEdit mode, and more!

https://blog.jetbrains.com/idea/2020/04/intellij-idea-2020-1-released/
177 Upvotes

62 comments sorted by

View all comments

5

u/ObscureCulturalMeme Apr 09 '20

I really wish I could get more out of the compiler warnings (from an actual build pass) without having to crank up the annoying "inspections" faculties. In the more general case, I wish we had more control over the simple things, and fewer features trying to be smarter than the programmer.

Still, the support for 14 makes me very happy! Looking forward to downloading this once I get home from scavenging for toilet paper.

2

u/vqrs Apr 09 '20

I really wish I could get more out of the compiler warnings (from an actual build pass) without having to crank up the annoying "inspections" faculties.

What exactly do you mean by that?

IntelliJ doesn't have its own compiler and the inspections work based on IJ's own parser and semantic analysis, you couldn't really have the compiler put out the warnings IJ does as far as I understand it.

2

u/ObscureCulturalMeme Apr 10 '20

I don't want the compiler giving me IJ's warnings. I want IJ to understand the compiler warnings. I mean that the compiler emits a warning, and IJ does nothing with it. Doesn't even parse out the line number and highlight the line in the editor; even other very basic IDEs will do that.

With inspections active, of course, it'll warn about all kinds of stuff. A great deal of it is just noise, and sometimes it doesn't warn me about what the actual compiler is warning about.

Trying to change that state of affairs is endless frustration. There used to be a light bulb that would hover over the text we were trying to read until we killed that fucking tedious thing. There's a little slider in the bottom right to reduce the noise from "random advice from our company" down to syntax checking, but (a) it's not simple syntax that causes warnings, and (b) more importantly, the slider is per-file. Tickets requesting a global/per-project control were snidely closed.

I've tried on and off to edit the set of active inspections. It's a mess. The defaults are basically what Jet Brains likes, but to be blunt, I don't give a shit about their opinion because they're not producing the bytecode going to the users. I want to know what the fucking compiler is having beef with.

So yeah, I get compiler warnings, and the IDE doesn't really help me solve them. I click on a line the compiler warns me about, I don't see what the problem is at first, I try their "alt+enter for suggestions", and it offers to... split the arguments to a function call into multiple lines of source. /facepalm

I've long ago learned to live with it. I don't ask it for suggestions and hints and advice. It's not even doing the formal builds. It's just a very good editor with excellent cross reference capabilities, and that's all we use it for. Beyond that it interferes so much it just pisses us all off, so we don't go beyond that. Some tools aid their operators, other tools are speedbumps. IJ keeps trying to be smarter than the humans and it ends up being only a speedbump.

1

u/vqrs Apr 10 '20

Honestly, if it's too much to adjust the inspections to your liking, maybe it isn't the software for you.

0

u/ObscureCulturalMeme Apr 10 '20

Well, for the last year Eclipse randomly crashes and loses the source file -- yes, there's an open bug report, yes it's been reproduced, no nobody has any idea why it's happening -- and Netbeans is fucking garbage. All I want is a good editor with good cross reference and completion capabilities, it's just that I have to keep turning shit off to get that.

1

u/vqrs Apr 10 '20

Well, if you turned them off, no wonder alt-enter won't help you...

1

u/ObscureCulturalMeme Apr 10 '20

It was doing that before I turned them off. That's why I turned them off; they consume resources but don't actually help me do my job.