-
22 votes
-
How I write HTTP services in Go after 13 years
9 votes -
Does Go have subtyping?
7 votes -
Perfectly reproducible, verified Go toolchains
11 votes -
Backward compatibility, Go 1.21, and Go 2
11 votes -
Coroutines for Go
9 votes -
SourceHut will blocklist the Go module mirror
13 votes -
Go generics can make your code slower
3 votes -
Statically recompiling NES games into native executables with LLVM and Go
6 votes -
Understanding DNS resolvers by writing a simple one in Go
7 votes -
Go proposal: expression to create pointer to simple types
4 votes -
Native Mac APIs for Go
6 votes -
Automatic redaction of user data from logs and crash reports in CockroachDB
5 votes -
Writing the same CLI application twice using Go and Rust: a personal experience
7 votes -
Go team publishes draft design proposals for a new read-only filesystem interface and a standard way to embed files into Go binaries
2 votes -
Featherweight Go
3 votes -
Why Discord is switching from Go to Rust
17 votes -
An update on bradfitz: Leaving Google
7 votes -
(ESR) Notes on the Go translation of Reposurgeon
8 votes -
Go 1.14 Beta 1 is released
4 votes -
The Principles of Versioning in Go
7 votes -
Go Turns 10
6 votes -
Faster ZIP Decompression
8 votes -
Working with Errors in Go 1.13
7 votes -
Go Proposal Process: Representation
4 votes -
Introducing Ristretto: A high performance, concurrent, memory-bound Go cache
3 votes -
TinyGo - A Go Compiler For Small Places
9 votes -
Go 1.13 Is Released
6 votes -
Next steps toward Go 2
6 votes -
Go is Google's language, not ours
15 votes -
Better x86 Assembly Generation with Go
4 votes -
Rust is not a good C replacement
27 votes -
Go 1.12 is released
11 votes -
Ian Lance Taylor: “Go intentionally has a weak type system, (…)”
Recently, Ian Lance Taylor, one of the most productive contributors to Go and, IIRC, the original author of gccgo, has written a very interesting comment on his view of the language: (…) Go...
Recently, Ian Lance Taylor, one of the most productive contributors to Go and, IIRC, the original author of gccgo, has written a very interesting comment on his view of the language:
(…) Go intentionally has a weak type system, and there are many restrictions that can be expressed in other languages but cannot be expressed in Go. Go in general encourages programming by writing code rather than programming by writing types. (…)
I found this distinction, writing code vs. writing types, very insightful. In my experience, in a language like Rust or (modern fancy) C++ the programmer is constantly forced to think about types, while when I program in Go or C, I almost never think about them. Types are, in fact, almost always obvious. It is also interesting that languages like Haskell and Idris explicitly expect the programmer to program with types.
What do you think?
9 votes -
Staticcheck 2019.1 released: a static analysis tool for Go programs
4 votes -
Go 2 Draft Designs
14 votes -
Go 1.11 released
8 votes -
Michael MacInnis: Oh a new Unix shell - BSDCan 2018
6 votes -
Tweeting for 10,000 Years: An Experiment in Autonomous Software
6 votes -
A talk about the Golang garbage collector from the International Symposium on Memory Management
4 votes -
Notes on structured concurrency, or: Go statement considered harmful
11 votes -
So who's using Rust, Go, Dart, D, or other less used or esoteric languages?
And what are you doing with them, I want ti know and I think others do to.
20 votes -
What is Software Engineering? (Go & Versioning, Part 9)
5 votes