How similar is the Go development process to Java/C# development?

Question

go

I switch with unity3d in the web, I have no experience in the web. Asked a couple of Javis friends what their job is. received answers that basically fix bugs. Moreover, the software is so large that it can often take a week or two and a lot is done at random. Plus a zoo of dozens of frameworks.

Is Go development like this? Or is there less code and the emphasis is on algorithms and multithreading? From what I googled, the Go niche is where performance is needed.

Answer 1

The language is simple with a powerful resource utilization model:

• used for all kinds of threshers
  
• any small functionality
  
• for busy servers
  
• in the general case, it differs from Java / C #, since it is not convenient to develop business logic, it is too simple and it is very expensive to write one
  
• all sorts of utilitarian things are written and bottlenecks due to simplicity
  

Answer 2

The hype around Go has already passed and it has taken its niche for which
a penny performance boost was intended, which gives Go does not justify the laboriousness of web development on it

Answer 3

More into algorithms and multithreading (strength) . Go is simple, understandable, because of this you don’t have to scold yourself, as in Java or Sharpe. You will spend more time on mental processes and application logic, and not on writing code. Basically Goshka - servers, microservices and quite a monolith, but mostly microservices. High load items. As for legacy, it is everywhere. On Go, it is much more difficult to meet legacy than on Java, and dealing with legacy on Go is much more pleasant than on Java. There is no particular zoo in Go: everywhere there is a standard lib, gin, gorilla, some kind of logger, some kind of format parser, and so on.

Answer 4

It all depends on the company - somewhere the development is actively going on, and somewhere the legacy is supported.
But given the fact that Go is more recent, the chance that you only have to fix bugs is extremely small.

Answer 5

For development in java, I would pick up a synonym for bureaucracy. Each of your ideas has already been implemented once and there are a lot of manuals and rules on how you should write it in your application. Go in this sense is a younger and simpler approach to development, but the downside is convenience. You will have to write various sorting, filtering data yourself or use fairly primitive means. If I were you, I would pay attention to Kotlin, in my opinion it is something between java and golang.