4 ms·

I've been really productive in Python in Javascript but Golang as slowly eroded away at those, now it's my primary language for most work. I do lots of backend

I've been really productive in Python in Javascript but Golang as slowly eroded away at those, now it's my primary language for most work. I do lots of backend web dev and I've recently started writing Lambdas in Go and find it superior to Python - better performance overall. I've found that it takes me longer to write code in Go than Python and the code is more verbose, but I have a very high rate of first-compile success. Compiler catches most errors I'm likely to make. I've written about 6 small services in Go now and 1 med / large sized one.

mettamage 5y ago
Interesting, I've noticed that the strong typing in Go does really help with getting that compile to work. I've worked in a medium Go codebase (one might call it big, it's on the edge). I sometimes had a really hard time getting a particular value from a variable. The problem was that the way the code was structured, I couldn't know the type, but in the debugger I did see that the value was there in memory. The senior Go software engineer told me to make the type global, but I don't know what to think of that to make any type global the moment multiple very far away source files need that particular form of type information. Another thing that I've seen that helps with Go productivity is the relentless focus of only one way to do things. Edit: I also think what is amazing about Go is the whole "everything sensible is baked in" type of thing. You may disagree if it's sensible. But I like being able to immediately write tests, or write HTML templates, etc.
- potta_coffee 5y ago
  Project structure is one of the things about Go that I didn't like. Because the community emphasizes the standard library over frameworks, and the import system was a little different, I really struggled with figuring out how to structure new projects. I'm not necessarily a Go fanboy, it's not exactly the most fun code to write but it's been a valuable tool for me.

mettamage 5y ago

Interesting, I've noticed that the strong typing in Go does really help with getting that compile to work. I've worked in a medium Go codebase (one might call it big, it's on the edge). I sometimes had a really hard time getting a particular value from a variable. The problem was that the way the code was structured, I couldn't know the type, but in the debugger I did see that the value was there in memory. The senior Go software engineer told me to make the type global, but I don't know what to think of that to make any type global the moment multiple very far away source files need that particular form of type information. Another thing that I've seen that helps with Go productivity is the relentless focus of only one way to do things. Edit: I also think what is amazing about Go is the whole "everything sensible is baked in" type of thing. You may disagree if it's sensible. But I like being able to immediately write tests, or write HTML templates, etc.

potta_coffee 5y ago
Project structure is one of the things about Go that I didn't like. Because the community emphasizes the standard library over frameworks, and the import system was a little different, I really struggled with figuring out how to structure new projects. I'm not necessarily a Go fanboy, it's not exactly the most fun code to write but it's been a valuable tool for me.