Go logo

The GoLand Blog

A cross-platform Go IDE with extended support for JavaScript, TypeScript, and databases
Download
News

Help us Choose a Name for our Go IDE

Andrey Cheptsov
Andrey Cheptsov

As you may know, Gogland is the codename for our new Go IDE that we’re building on top of IntelliJ Platform. While we’re working hard on the IDE itself, trying to make it fast and smart, we’re also brainstorming its final name. This is something you can contribute to!

Gopher illustration by Renee French

Gopher illustration by Renee French

Please share your suggestions with us here in the comments, or by replying to the official tweet or Facebook post.

The name will be chosen by the JetBrains team hopefully in the next week. Later we will announce it with one the upcoming posts.

What name are we looking for? Something easy to pronounce. Easy to spell. Ideally, a one-word name (that hopefully isn’t someone else’s trademark). On the other hand, don’t be limited by any rules. Suggest what you think is best. All ideas are welcome!

If your name is chosen, you stand to get a spiffy prize (it’s a secret for now) along with a free 1-year subscription to all JetBrains products!

Go!

Gogland EAP 15: Inspections, Intentions, Performance, IntelliJ 2017.3, and MoreGogland EAP 16: File Watcher, Tons of New Inspections, Smarter Navigate to Test, and More

Discover more

What’s Next: GoLand Roadmap 2022.3

We’ve just released a new version of GoLand and are ready to share our plans for the next major update. If you haven’t yet checked out what we packed into GoLand 2022.2, here’s a brief overview. The second release brings: New quick-fixes, a bunch of code inspections, and other improvements for generics.A quick-fix for grouping multiple use directives in go.work files.The ability to run fuzz tests and explore failing ones inside the IDE, as well as a quick-fix to immediately change the Go SDK if the current SDK doesn't support fuzzing.Support for new features that came with Go 1.19

Ekaterina Zharova Ekaterina Zharova

GoLand is looking for Developer Advocate and Technical Content Creator

Introduction The GoLand team has opened two positions: Developer Advocate and Technical Content Creator. Please refer to the position descriptions for the requirements and expectations, and be sure to check out this blog post to find out what it’s like to be a developer advocate at JetBrains. Even though it was written in the pre-COVID era, many of the points are still true. In this post, I’d like to focus on why we need these roles on our team and the key differences between them. The post might be interesting to those who want to apply for these positions or are just curious about how thi

Artem Khvastunov Artem Khvastunov

What’s Next: GoLand 2022.2 Roadmap

Last week we released GoLand 2022.1. The first major update brings support for generics and Go workspaces and new features for working with microservices, such as the ability to see all endpoints in a dedicated tool window and to generate HTTP requests right from your Go files.  Learn more on our What’s New page, where you’ll find a full overview of the release along with GIFs and screenshots. If you prefer a more interactive approach to learning about these new GoLand features, feel free to complete the What’s New in GoLand 2022.1 tutorial on the Welcome screen.  Last but not

Ekaterina Zharova Ekaterina Zharova

What’s Next: GoLand 2021.3 Roadmap

A few weeks ago we introduced a new version of GoLand – 2021.2. In this version you will find the new abilities to control the behavior of go list, manually reload the go.mod file after you’ve made changes, and run default built-in and gofmt formatters one by one. You can also explore new Go 1.17 features, from moving the //go:build lines to the top of the file immediately (as the new syntax requires), to converting a slice to an array pointer. The new version brings changes for the VCS, such as the ability to sign commits with GPG keys, UI enhancements, a Preview mode for the debugger, and mo

Ekaterina Zharova Ekaterina Zharova