That's true, but being able to quickly click on the line that has the error and have your editor navigate to the file automatically is slightly more painful to setup, and is bespoke for whatever tool you are using.
My point was just that a tight integration between language and IDE/editor makes the overall language experience much nicer. For example:
Racket/Dr. Racket Python/Pycharm Java/Intellij Emacs lisp/Emacs
In the event that the tool doesn't output in one of the common formats, it's usually just a regex; again I had this in Vim for several different languages back in the 90s.
>> My point was just that a tight integration between language and IDE/editor makes the overall language experience much nicer.
I agree (happy SLIME user here), but it often seems like I'm in the minority. I've literally never met someone in person besides me that uses pycharm, and you are about the 3rd person online I've seen mention it in a favorable light.
Vim, for example, has a plugin called "syntastic" that is kind of a meta-plugin aggregating lots of these, and indeed it seems to have support for nim error checking.
LSP is a nice step forward, but people had error highlighting for decades before it was invented.
[edit]
Doesn't change anything above, but someone pointed me at ALE which is a newer tool that can run lint engines asynchronously (using interfaces that didn't exist when syntastic was created). For vim specifically that may be a better tool, but I haven't tried it yet.