[Dinius]

So basically just the existing Go plugin (give or take a feature or two) shoved into a standalone editor which, knowing Jetbrains, is sure to be flust with new bugs for the foreseeable future..

Not to sound negative or anything.

[AsyncAwait]

They'll probably start that way, but will add more features closer to a 1.0 release. Every one of their IDEs starts simple and then develops to one of the best in the industry, I don't see why this should be any different with Go.

[bubblesocks]

Best in the industry? I wouldn't go that far. Considering how slow JetBrains tends to be with fixing bugs (I logged a few against PyCharm in 2011 that still haven't been fixed, which is why I don't use it anymore), how unstable their environment can become when debugging, and how they refuse to address Dvorak key-mapping issues in macOS, I think the furthest I'd be willing to go is that JetBrains makes some IDEs.

[Hates_]

Sounds like there's actually a lot more: https://www.jetbrains.com/help/go/1.0/faq.html#d3e52

[geodel]

It also mentions formatting similar to 'go fmt'. So it is not integrating Go tools natively. Seems to be useful for people who love more mouse clicks than keyboard. Go's excellent tooling, suitable for automated and fast workflows will not be utilized here.

[dom0]

> who love more mouse clicks than keyboard

Did you ever use a JetBrains product? No? I thought so.

[geodel]

I use Intellij IDEA all the time for Java and I also learned a few keyboard shortcuts along the way. So no need to think for me.

I still think Go is far more keyboard/CLI oriented as compared to Java. From their description it looks like they are shoving some Go stuff on to a Java IDE. It is still good for people craving a Go IDE in Java mold.

[gtaylor]

Eh, as a PyCharm user I never see much of anything suggesting Java. JetBrains does a great job with these editors.

[MikeKusold]

I'm very disappointed in that decision. It should use the native `go fmt` tool. On some code bases, we use CI to ensure that `go fmt` was ran on checked in code. If there is even a slight difference between IntelliJ's implementation and `go fmt` then it will cause CI to fail.

[dlsniper]

There are technical reasons for not doing that. Most important one being that it can do formatting on the fly and not have your cursor jump around when formatting. So your experience will actually be a whole lot better than any other editor. And if they say that it's going to be on par with gofmt it will be on par with gofmt. Do consider that they might actually know what they are doing.

[AsyncAwait]

I think they have a technical reason for not being able to implement 'go fmt' directly.