Editors need to be able to support our very unique way of storing code (monorepo).

I had the exact opposite issue past weeks. Using a Go monorepo, none of the 'normal' go tools worked. In fact, auto complete did not work with go modules at all for months, I only recently got alternative language server somewhat working and they only work for a single modules repository.

On the other hand, Goland (or Go plugin for IntelliJ) handled modules flawlessly the whole time and they handle monorepo full of go modules flawlessly as well.

Go team is now working on an offical LSP server called gopls and have in fact just recently publishes first alpha release so hopefully, the situation will improve in a while.

Yes, using gopls is the way how I finally got some support for modules for the first time since they were released (single module only though - useless for monorepo).

Google and Microsoft use monorepos, and it's so unique that nobody in either company can use JetBrains?

I'm not a Googler so I don't know for sure, but I'm pretty sure Jetbrains IntelliJ is pretty heavily used at Google considering Bazel has really good support for it and it is the basis for Android Studio... so yea, sounds more like a self-inflicted problem than a real problem.

I'm a recent convert from Visual Studio to Rider, and I love almost every aspect of it. The bit I really don't like is how it handles source control - it seems to try to generalise every source control provider, and I find the git functionality to be a real PITA - it automatically stages any new files, and I've encountered many quirks that I just don't like.

My solution thus far is to use VS Code for all git functions (yes, I prefer a UI over command line for git), and use Rider for everything else. It suits me well - VS is basically my dream git UI!

Having said that, I still wish JetBrains would fix the car-crash of their got functionality...

>it automatically stages any new files

no it doesn't? it explicitly asks you whether you'd like to "add" the file.

Strange Rider seems to stage all new files without asking for me. I'm on 2019.1.EAP1, but I had the same behaviour on 2018.3.4. It might be configurable, but I don't see anything in the git config within Rider.

There's a plugin to support the large monorepo at the FAANG i work for, i would expect there is one at the other too. A lot more people use the jetbrains products than you think at these companies.

...but you can exclude directories in jetbrains tools?

Funny, ability to output fully functional Jetbrains configs is a core requirement for our early-stage corporate Go monorepo.