[darren0]

I programmed Java for 15 years in mostly eclipse. The past 3 years I've been doing go in vim. Just recently I switched to Gogland for go, which is a full blown IDE. It's been life-changingly good. I forgot just how nice it is to have proper tools that just work. So even in a "simple" language like go, an IDE can make a huge difference if you care to learn it.

[fiddlerwoaroof]

I've had mostly the opposite experience: I've used vim and emacs/evil-mode for 10 years or so now and now, since my day-job involves lots of pair programming, I've had to use tooling that other people are comfortable with (e.g. Atom/VSCode/Intellij) and, the only places I find a clear win over my old tools are places where I rely on Intellij's features (auto-implementation of interfaces and other boilerplaty issues with Java). When I've worked in Javascript/PHP/etc., I've never found the overhead of an IDE to be worth it.

Also, I haven't written much go, but my general impression is that the language trends on the verbose side because of the lack of things like generics and it's error-handling strategy, so I'm not too surprised that it's more pleasant to use an IDE for go than it is to produce it manually.

Also, most of my side-projects are in Common Lisp and, I've yet to find a "mainstream" programming environment that's more pleasant to work with than my SLIME/emacs setup for writing CL.

[omaranto]

Unless I misunderstood you, this does not sound like the opposite experience, but the same experience. You say that (for Java) you found the IDE, IntelliJ, better than the editors vim, Emacs, Atom, VSCode.

[fiddlerwoaroof]

No I was saying that I found that certain kinds of languages (verbose, boilerplate-y languages like Java) benefit from an IDE to automate the boilerplate away while more concise languages (like Common Lisp or Haskell) benefit very little from having an actual IDE vs. a simple text editor.