Go

“every time we use a compiled language like Go or Rust or C++.”

“Operating a Go gateway in production (single machine, ~20B tokens/month across several upstreams)”

“converting to Go, Elixir/Phoenix, or Rust/Axum depending on the app”

“similar to how we were using Go, but now we have a language less.”

“Ended up rebuilding in Go, the perf gains weren't worth it”

“here's the 2.0.6 AI port... it's been running beautifully in prod in Blues' Notehub”

“We replaced our usage of go list with a custom package import graph parser using the std lib parser packages”

“I tried to do it and I can tell you that it works and it works for even the most latest versions of golang”

“I looked at gccgo when porting the runtime to n64, but at the time it wasn't updated since go1.18.”

“Runner-0: T=0s... Zero network, zero clock drift. Just local time.Sleep().”

“I'm assembling systems out of really small "services" (written in Go) that Claude Code can immediately run”

“I work regularly with Go, React, TypeScript, and I don't miss VSCode.”

“for the pretty bog-standards ways I'd been using Rust and Go.”

“As someone who writes both Python and Go (and I've been using Python professionally since 2005)”

“I decided to build my website from scratch in Go, because this way I can allow people to download, share, and reuse content more easily.”

“I'm still relatively new to Go, but I've never seen closures used that often thus far in production code.”

“all our code in production hammering away concurrently on a couple of client instances”

“I used to write a lot of C#. I used to write a lot of Go.”

“super helpful for someone like me who recently started building services in Go.”

“the services we run are typically self-contained golang binaries that we can deploy with bash onto baremetal.”

“the power of SQLC is that anyone who can write SQL can work on the CRUD part of your Go backend”

“I have way too much custom elisp to build and debug Rust/Go/C++”

“several optimizations at both the Go and Postgres levels. On the Go side, we use prioritized work queues”

“With Go generics - and equivalent in most other languages - you can write a 5-line helper function”

“I've been using mise at work to manage go versions, it's been good although a little confusing and undocumented at times.”

“The userspace part that's in Go and not in other languages that we use is the wgctrl library.”

“trying to do them in Rust and Golang in an effort to either learn to like/tolerate Golang (because we use it at work)”

“had prior exp in php, python, java, Go, and Typescript, and enjoyed most of them”

“Using a JS runtime with a dependency on cgo means your Go program loses the (huge) benefit of cross-compiling”

“I have a fair bit of experience writing tests for concurrent code that uses timers on Go.”

“Our services are all golang so beanstalk eventually was getting in the way”

“I built my core logic in Golang, and then decided to wrap it in an Android app.”

“any more complex logic (e.g. batching, parallelization, health checks) was done in a short Go program.”

“I'm back to glorified fmt.Printf statements that hopefully have enough context that the 40 min build/deploy time was worth it.”

“I just noticed some bug in production caused by wrong typing in Go and I need to fix it.”

“I have been using Ruby for twenty years, Rust for eight, golang for nine, and C for twenty-six.”

“things are versioned like any other Go program, builds are 100% reproducible.”

“we already implemented a golang OTel log handler for the external case”

“we migrated from .NET Core 3.1 to Go back to .NET 6 recently”

“Something that was lost when we moved to modules - the system is still the same”

“we replaced/will replace all microservices with Go.”

“We figure that the use of go alone creates some important portion of that overhead”

“Wanted to learn Go so recently started working on a CLI packet capture tool like tcpdump”

“we migrated an old Python API to Go, with the same interface contract”

“Nowadays I use Elixir and Golang for prototyping and the end products either remain that or get rewritten in Rust.”

“I've worked in prod with all the cool languages (Scala, Haskell, Rust, Go, etc...)”

“I've experimented with golang before as I wanted something easier to scale”

“For APIs we already have a part of this data, as most server in Go have the number of requests for each endpoint.”

“In the past two years I've done hands on keyboard coding in Python, C#, JavaScript, and Go.”

“This is our first experience generating docs for a single project that spans C, C++, Python, Java, and GoLang”

“find it to be no problem in practice to write integration tests for our pieces of Go code that calls the SQL queries”

“We had some Go code, but replaced it with Elixir.”

“at my previous job it was a mix of PHP / JS (Dojo), Go, Typescript”

“With Go + stdlib template.”

“Go for random stuff where people were able to shoehorn it in.”

“After we switched tests to the Golang cucumber implementation”

“We've replaced nginx/lua with a cache server (for video) written in Golang”

“we have already do this in prod. type HandlerFuncErr func(w http.ResponseWriter, r http.Request) error”

“we migrated all erlang, golang and nodejs code to edge workers on cloudflare and simply did not need to run containers anymore”

“I've used each of those languages and also use Kotlin both on the JVM and in the browser.”

“the actual version we run nowadays is using UEFI and written in Go (installer) + Python (API that generates the ISO on demand)”

“kept API as we migrated backed to go (via a terrible course through nodejs)”

“we just use an ODBC library in go to connect”

“we're slowly rewriting a legacy Perl code base to Go HTTP services”

“in case anybody wants to go down the rabbit hole of shit you should definitely not use in production (but we did anyway)”

“We had Go libraries to do this, and it would have been nice to be able to just call into that.”

“Almost every api is in Golang, and we replaced Python with Go to run the models.”

“This posts shares one of the patterns we use in Go codebases to mock client libraries.”

“a special goroutine reads this table and pushes new events to the message broker”

“I've written Go programs for Fortune 50 companies, as well as complex personal projects”

“We have a mixture of python, java, go, protobuf, and node.”

“I diplomatically agreed to use Go to consume the data and serve the API.. so that's been time consuming.. but fun!”

“there weren't different scopes for each goroutine and the error messages got mixed up”

“managing 4 college grads on an enterprise financial app in a programming language none of them had ever seen before (Go)”

“We use Go, and we will test by using test fakes - a struct that matches an interface is created in the test file.”

“A few years ago I had spent a year working with a Go project that made heavy use of one of the (then) popular Go ORMs.”

“with basically this system for both a rails app and about 20 other go apps.”

“I write Lambda functions in golang.”

“we did try a lot of other backend stacks (Go, PHP, Clojure, Python, ...)”

“we also worked with python, nodejs, some Go.”

“We moved to Go 1.15 up from 1.13 for security fixes and ecosystem improvements”

“other languages and frameworks I've used in prod (Golang, Dotnet, Dotnet Core, Node, Ts-Node, Rails, PHP, etc)”

“I've been using Go and Rust for so long i've forgotten what classical inheritance is actually useful for”

“We don't work in Python so I've not used Chalice but I'll see if it can inspire our Go tooling.”

“I've started this as a hobby project for practicing my Golang skills.”

“At my day job, all the stuff we put in Docker is either Python (generally portable), Java (generally portable), or Go”

“the payloads and responses are directly derived from the Golang structs”

“If go's Prometheus library had an easy way to run "metric.CurrentValue()", I would have tested it... but it didn't”

“Our systems are mostly in C++, with some in Go such as crawler.”

“In my codebase at work there are a few cases where code is (poorly duplicated) that would benefit from a proper generic solution.”

“I've also contributed to the linux kernel, chromium, the go programming language and a number of others.”

“It's Postgres under the hood. The key-value service itself is Go and we run it on GKE alongside some of our other services.”

“our projects at work keep growing with helper files... go.mod and go.sum”

“We run our own analytics solution based on a js library, a small go app and ClickHouse for data aggregation.”

“why we moved to go.”

“We also have ~20 Go services that are also deployed via Nix”

“when we compare go to 0.2, tokio uses less cpu consistently”

“I've been using Go for middlin' size projects for several years, and recently wrote about a 10K SLOC program in it.”

“I've tried Python, Go, Rust, Julia.”

“we have part of the codebase in Go that we are migrating to Nim at the moment”

“new services written in Go”

“a small piece of our GraphQL schema is already in Go running in production.”

“I've been using Makefiles for Go development basically since I started with the language.”

“(I've tried Rust and Go) the lsp-mode experience is flawless”

“We have an in house Golang server binding to c++ for serving pytorch neural nets”

“And this is coming from Go user and enthusiast.”

“I went for GTK3 in Go (Gotk3) and kind of regret it.”

“The code is a fork of https://github.com/google/zoekt, written in Go.”

“We have a senior dev whose software caused a memory leak in prod. ... I wouldn't be surprised if his code is causing a goroutine leak.”

“I stopped approving new Java projects in my team 2 years ago after we switched to Go.”

“We switched over from our old NodeJS backend to a new Go backend recently”

“We have a Go service that is deployed directly to EC2 with a Makefile from its source repo.”

“I've been using K8's for over a year and have built some golang apps.”

“I've played with them in the past, but not spent enough time with them to be confident using them in production.”

“I learned and brought in production the followings: AWS Cloudflare and Lambda (with Go)”

“I've disabled megacheck, which didn't work with Go modules the last time I tried it.”

“but our control plane is Go / C.”

“we run on elm and a mix of Haskell and go”

“I am one of the relatively few people who's been doing Go in production since pre-go1.0.”

“Our govars also sets the path on where to find our conf.yaml for env config.”

“Just checked memory use on some services we run on Go, Node, and Java.”

“it was written in Go”

“We run binaries on our lambda instance with a go-based function”

“single, static binaries (like we do in 90% of cases with Go)”

“Two years ago we switched from PHP to Go, which definitely helped.”

“we've moved to the structural recommendations in the Go documentation a long time ago”

“We rolled our own go program that just does go tpl substitution in yaml”

“I forked the encoding/xml library once so I could add tag stack depth limits and size limits for tags and text nodes, so I could use it to write an XML validator”

“I've been using a starter kit[1] to build our API.For database access using Modl[2]”

“I have a lot of experience with Golang and built many tools, and it always felt more natural to me when there is no database/models involved.”

“In Go, there _are_ pointers, and students get used to thinking about memory addresses as values.”

“I have put Java/Scala/Go/Erlang systems in production, and rarely have I have ever had to worry about GC tuning.”

“Then we moved to Go and now we are in Rust.”

“Most of our stack is Go, but we use the excellent Faye library written in Node”

“it's written in Go, my main language, which is definitely a plus if you're a gopher”

“We do a decent amount of go at the company I work for.”

“We run a simple go program on the postgresql server that LISTEN's, queries, pushes to REDIS”

“This is with CGO enabled code, which isn't optional as it's from the libraries we use”

“a combination of node js, golang, and Python/flask apps”

“we use Ruby, Go, and elastic search”

“I've been developing in Go for the past 4”

“although we use it all the time on our go apps”

“On some code bases, we use CI to ensure that `go fmt` was ran on checked in code.”

“Some of the pain points are related to Go's sql interface”

“Our Platform team uses Golang extensively. We use it together with gRPC”

“The reference implementation is quite modular Go, which is nice for portability”

“I use both on a regular basis and I've been using Python for over a decade.”

“At Cloudflare it's our default router for internal APIs, which are all written in Go.”

“Ensembles of decision trees (boosted, bagged) in golang. It's a project I started as a research platform”

“Yep we run Go for some infrastructure and ops kind of things”

“I'm not using Apex or any of the other frameworks, just plain Go code wrapped by the JS function.”

“We've run through PHP, Rails, Node, Python (Django) and lately Go.”

“"old fashioned" ETL scripting in Python (now some Go) on the backend.”

“We were Python, Java, and Go and all were terrible.”

“We do Bitcoin and Blockchain development. Full stack JS and Go.”

“I've been successful in introducing a Golang web service.”

“I write mostly write C, Bash, Python, Go, Puppet.”

“So, we're slowly transitioning to a Go backend with a slim Node.js layer to form the very friendly API”

“Ive not used it in production but have contributed to it.”

“We started using Prometheus for a Go-based app in production a few weeks ago.”

“Inside Google we have been setting GOMAXPROCS=runtime.NumCPU for many years because most of the Go programs we run are highly concurrent network servers”

“In Go we achieve the same result in a more simple way using the defer statement.”

“Running 200 microservices in production. 199 of which are Go.”

“Using Go in production”

“I have written this and been using this in production for quite some time”

“I believe we're the only ones doing using Go in production at Facebook.”

“Lein and GO deployment”

“I am a Go developer; you have no idea how many problems people have had with the homebrew package.”

“We replaced Intruder with a command-line tool written in Golang”

“we run some asynchronous tasks with Go now, specifying to replace a few things that were done by Celery previously.”

“We're in the process now of switching to a simple go-based HTTP proxy”

“I've been using go for some time but I've never seen this”

“I've been using the excellent goandroid to develop Android apps with Go and the NDK.”

“the code we run on the servers is optimized and vectorized Go/C++ code”

“will do so slowly (using Go otherwise).”

“We run a Go based lockserver at Tinkercad but we haven't got around to adding redundant storage.”

“We also use Go and not Node.js for the backend”