Report finds Go is becoming more critical to a company’s success

by Jeremy

[ad_1]

The Go programming language is making its way to more enterprises and businesses. The 2020 Go survey results found that 76% of respondents are using Go at work, and 66% stated it’s becoming critical to their company’s success.

Additionally, 91% of respondents would like to use Go for their next new project, and 89% find it is working well for their team. The results are based on 9,648 developer responses. “Understanding developers’ experiences and challenges helps us measure our progress and directs the future of Go,” the team wrote in a post

RELATED CONTENT: Why developers love Go

The language’s top features, according to respondents, include build speed, reliability, using concurrency, CPU usage and editor support. VS Code is the preferred editor with GoLand following closely. Respondents are also having success with its cloud services, debugging and modules. 

Overall, 92% of respondents say they are satisfied or somewhat satisfied with the language. Eighty-one percent of respondents find they are very or extremely productive with Go, and 93% stated it took less than one year to become productive with Go. Of that 93%, 31% found themselves more productive between one week and one month of using Go, and 33% were more productive between one month and three months. 

The report did find a downwards trend of those who stated they feel welcomed by the Go community. Only 78% of respondents reported feeling welcomed this year compared to 84% in 2017. When asked what would make them feel more welcome, respondents stated more learning resources and docs, improved contributor experience, and maintainer attitudes. 

The top use cases for Go include: API/RPC services, CLI, libraries or frameworks, and web services. 

The top reasons for not using Go include working on a project in another language, the team prefers to use another language, and Go lacks a critical feature necessary to do their work. Top challenges include lack of generics, modules/package management, and problems with the learning curve. 

[ad_2]

Source link

Related Posts

Leave a Comment