Go hit production "1.0" just a few years ago. It takes a long time for a new language to see adoption in large numbers, especially in enterprise. Its also important to remember that Google created Go for itself, as a more efficient and cleaner replacement for Python.
That said, there are a good number of companies using Go for systems-side applications and services, which is where Go really seems to have its niche. I have used it to create a MMORPG server and its been very stable and performant. My company has used it to create a scalable api engine and for a few other projects like integration middleware, etc. Overall its been a very useful tool.
The time-to-production on a new project is far less than most other compiled languages, and its easier for fresh grads to pick up and be productive with than something like C or C++. The simplicity of the language and built-in documenting system is nice and helps us reduce cost on the QC and code review side, since its quicker to read (both for the compiler and a human).
The language has some warts, and the ecosystem is still fairly young, so you may end up creating a library that in other languages you'd just pull in from somewhere else, which has its pros and cons. Thankfully Go makes it pretty easy to subdivide into libraries and to pull in third party libraries from various hosts. In 1.5 they added 'vendoring' which I think was a much needed enterprise feature. Vendoring essentially lets you maintain a fork of specific version of a library within your own project source. For enterprise this is important, as you wouldn't want to be stuck refactoring off-schedule if an external library has a breaking change in a new verison. It was possible to do this before without vendoring, but now its much cleaner and easier to set up and track.
TLDR; Yes, companies and people are using it. Its still a relatively new language and has a young ecosystem. It performs well and is easier to get fresh grads up to a productive level with. Is it going to have a future? Yes. Will it replace something like C? Doubtful. Will it compliment C well? Yes.
Side-note: Go won't disappear. Look at D, which has an even smaller following and is quite old at this point. Languages generally tend to stick around. Will there be tons of Go jobs in the future? Who knows... but for a good developer, knowing the specific language isn't a barrier to getting the job anyway.
Go hit production "1.0" just a few years ago. It takes a long time for a new language to see adoption in large numbers, especially in enterprise. Its also important to remember that Google created Go for itself, as a more efficient and cleaner replacement for Python.
That said, there are a good number of companies using Go for systems-side applications and services, which is where Go really seems to have its niche. I have used it to create a MMORPG server and its been very stable and performant. My company has used it to create a scalable api engine and for a few other projects like integration middleware, etc. Overall its been a very useful tool.
The time-to-production on a new project is far less than most other compiled languages, and its easier for fresh grads to pick up and be productive with than something like C or C++. The simplicity of the language and built-in documenting system is nice and helps us reduce cost on the QC and code review side, since its quicker to read (both for the compiler and a human).
The language has some warts, and the ecosystem is still fairly young, so you may end up creating a library that in other languages you'd just pull in from somewhere else, which has its pros and cons. Thankfully Go makes it pretty easy to subdivide into libraries and to pull in third party libraries from various hosts. In 1.5 they added 'vendoring' which I think was a much needed enterprise feature. Vendoring essentially lets you maintain a fork of specific version of a library within your own project source. For enterprise this is important, as you wouldn't want to be stuck refactoring off-schedule if an external library has a breaking change in a new verison. It was possible to do this before without vendoring, but now its much cleaner and easier to set up and track.
TLDR; Yes, companies and people are using it. Its still a relatively new language and has a young ecosystem. It performs well and is easier to get fresh grads up to a productive level with. Is it going to have a future? Yes. Will it replace something like C? Doubtful. Will it compliment C well? Yes.
Side-note: Go won't disappear. Look at D, which has an even smaller following and is quite old at this point. Languages generally tend to stick around. Will there be tons of Go jobs in the future? Who knows... but for a good developer, knowing the specific language isn't a barrier to getting the job anyway.