DEV Community

Evan Lin
Evan Lin

Posted on • Originally published at evanlin.com on

Go Developer Survey 2019 (Part 1: Pain Points)

Background

The Golang Association recently released the results of last year's developer survey.

Go Developer Survey 2019 Results

tl;pr (Too Long, Please Read) I know this survey is long, you definitely won't read it. I'll help you pick out a key point every day.

“Pain points”

This survey investigates the reasons why you don't use Go in your projects. Here are the top three, along with a comparison of the 2016 survey report and the 2019 numbers. You might have thought the first place would be Generic, but it's not!

-

First place: The current project is in another programming language (58% -> 56%) quite reasonable~ Switching to another language to rewrite the entire product or project. Either you leave, or the boss tells you to leave. XD

-

Second place: My team (boss) (project) prefers other programming languages (45% -> 37%) This is quite interesting. In fact, the community often hears "The boss told me not to use Go" or "The boss likes other languages." These issues need continuous introduction. wwww But it's good that the numbers are decreasing.

-

Third place: Go lacks some language features I need (16% -> 25%) Finally, we get to the more controversial point, which is whether Go Generics make people feel troubled during development. However, the proportion has increased, possibly because there are indeed related needs after developing for a period of time.

Welcome everyone to discuss….

Top comments (0)