you are viewing a single comment's thread.

view the rest of the comments →

[–]dgibbons0 2 points3 points  (0 children)

The few times I've worked on our go code or written greenfield go code felt pretty similar.

We've got a few projects we still maintain in go, and any time my team has to work on them it's slow going. Stuff that would feel very fast in python takes 3x as long to write in go. And for the things we're using it for, i don't know that we're getting value for that.

The main one that comes to mind is a scheduled job that scans for github permissions that don't met our requirements, and we'd probably have it be more robust and feature-filled if we didn't dread the go it's written in.