# A Go Developer's Subjective Critiques of the Language

DevFeed: [A Go Developer's Subjective Critiques of the Language](<https://devfeed.tech/articles/go-is-amazing-so-here-s-what-i-don-t-like-about-it-41258.md>)

Original publisher: [Read original article](<https://www.evilsocket.net/2018/03/14/Go-is-amazing-so-here-s-what-i-don-t-like-about-it/>)

Author: Simone Margaritelli

Published: 2018-03-14T22:39:09Z

Content type: opinion

Language: en

Sources: [evilsocket](<https://devfeed.tech/sources/evilsocket.md>)

Topics: [Go Language](<https://devfeed.tech/topics/go-language.md>), [Programming](<https://devfeed.tech/topics/programming.md>)

Tags: [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [design-patterns](<https://devfeed.tech/tags/design-patterns.md>), [developing](<https://devfeed.tech/tags/developing.md>), [go](<https://devfeed.tech/tags/go.md>), [golang](<https://devfeed.tech/tags/golang.md>), [language-critique](<https://devfeed.tech/tags/language-critique.md>), [oop](<https://devfeed.tech/tags/oop.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [programming](<https://devfeed.tech/tags/programming.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

## AI overview

A Go programmer presents subjective criticisms of the language to offer a more balanced account of their experience. The author says Go may still be a better choice for several applications and does not frame the piece as a Go-versus-Rust debate.

## Source excerpt

After my last post and generally the kind of indirect advertising I'm doing to the Go programming language for a few months now, I heard about and talked with a lot of people who started being interested in the language, so for once I decided to write what I don't like about it instead, to provide a more balanced perspective of what's my experience so far and maybe let some of those people realize that Go is not the right choice for their projects after all. NOTE 1 It's important to say that some, if not most of the things I'm about to write are purely subjective and related to my programming habits, they do not necessarily represent so called "best practices" and should not be taken like so. Moreover, I'm still a Go noob, some of the things I'm going to say might just be inaccurate / wrong, in which case feel free to correct me and teach me something new, please :D NOTE 2 Before we start: I love this language and I already explained why I still consider it a better choice for several applications, but I'm not interested in an opinion war about Go vs Rust, or Go vs whatever ... use what you think it's best for what you have to do: if that's Rust go for it, if you think it's binary code you send to the processor by using your nipples to inject faults into some data bus, go for it, both cases, code and let code, life is too short for being a language hipster.