Why Go is not my favourite language

Summary

The author critiques Go, focusing on error handling, lack of scope-based resource management, and other language design issues. They compare Go unfavorably to languages like C++ and Python.

Key Takeaways

1. Go's error handling, using return values and panic/recover, is likened to exceptions, requiring exception-safe code.
2. The absence of automatic resource management at the end of scope in Go necessitates the use of 'defer,' which the author finds verbose and less elegant than C++ or Python.
3. The author expresses frustration with Go's scoping rules and the need for 'make()' for maps and channels, questioning the language's consistency.

Statement Breakdown

• Claimed Facts: 40% of statements the article presents as facts
• Opinions: 50% of statements classified as editorial or subjective
• Claims: 10% of statements surfaced for additional reader evaluation

Credibility & Bias Reasoning

Credibility assessment: The article is a personal blog post detailing the author's opinions on the Go programming language. While the author presents technical arguments, these are subjective and based on their experience. The lack of external verification lowers the overall credibility.

Bias assessment: Go Programming Language Criticism. The article is heavily biased against the Go programming language, focusing on its perceived flaws and shortcomings compared to other languages like C++, Python, and Java. The author uses strong, negative language to express their dissatisfaction with certain design choices in Go.

Note: This article presents a subjective critique of the Go programming language. Reader discretion is advised, as the views expressed are the author's own and may not reflect broader consensus.

Credibility flag: Subjective Analysis

Claimed Facts (6)

• This is a factual description of how error handling works in Go.
• This is a specific example of how panic/recover is used in the Go standard library.
• This describes the standard practice for using locks in Go.
• This is a factual statement about C++'s resource management.
• This is a factual statement about Python and Java's resource management.
• This is a statement about the Go compiler's behavior.

Opinions (6)

• This is an analogy expressing the author's opinion on Go's error handling.
• This is a subjective assessment of the 'defer' keyword.
• This expresses the author's opinion on what should happen automatically.
• This is a subjective feeling about a language feature.
• This is the author's overall opinion.
• This is the author's overall opinion.

Claims (5)

• This is a rhetorical question implying a universal negative opinion, which is unlikely to be true.
• This is an exaggeration and generalization about Go programmers' behavior.
• The author presents this as obvious, but it's a technical detail that many programmers might not know.
• The author uses emotional language ('bloody useful') to emphasize their point.
• This is a subjective claim about the usefulness of external tools, presented as a fact.

Key Sources

• Author — Blogger