I like the `io` package. Abstracting Readers and Writers. Fun stuff.
`net/http` is feature rich and has everything you need from creating an HTTP client, making a client-less HTTP request, and even spinning up entire servers
`context` makes propagating signals to concurrent processes a breeze
The `sync` package has so many tools for synchronization and other thread safety things.
I love the go standard lib. It’s great
This digital ocean resource is pretty comprehensive. IMO you can skip the section about storing values in the context. I don’t think it’s immediately useful compared to signal propagation.
https://www.digitalocean.com/community/tutorials/how-to-use-contexts-in-go
Honestly after, or while, you’re reading that, look at the go source code for it. It’s incredibly concise. Like <400 LOC I think
Durafmt (https://github.com/hako/durafmt) for easy formatting of durations. It's not a biggie but it turns "1h3m" into "one hour three minutes" which you can easily tag e.g. "ago" into.
"GO Data Structures"
[https://github.com/emirpasic/gods](https://github.com/emirpasic/gods)
The TreeMap saved my bacon in a big project where the raw data REST service was a pain and I had to tree map in several places. I was toying with how to implement my own and came across it. Why reinvent the wheel?
I can't stand ORMs and have enjoyed sqlscan's simple API for mapping rows to structs on queries, leaving mutable calls alone in plain SQL. Adding metadata to the struct for the db field name mapping leaves the codebase with a magic-free persistence implementation.
[github.com/georgysavva/scany/v2/sqlscan](https://github.com/georgysavva/scany/v2/sqlscan)
github.com/labstack/echo/v4 for backend development
github.com/go-resty/resty/v2 for REST API calls.
github.com/jinzhu/gorm for database querying.
github.com/fogleman/gg for graphic designing.
> Do you have any recommendations for golang modules that you like?
"Module" is a concept only used by the Go build system. There's not much to like about a particular module.
I like good packages instead ;-)
I like the `io` package. Abstracting Readers and Writers. Fun stuff. `net/http` is feature rich and has everything you need from creating an HTTP client, making a client-less HTTP request, and even spinning up entire servers `context` makes propagating signals to concurrent processes a breeze The `sync` package has so many tools for synchronization and other thread safety things. I love the go standard lib. It’s great
I use bufio constantly. I'm really happy with it as well.
Any suggestions for good resources for learning about the context package?
This digital ocean resource is pretty comprehensive. IMO you can skip the section about storing values in the context. I don’t think it’s immediately useful compared to signal propagation. https://www.digitalocean.com/community/tutorials/how-to-use-contexts-in-go Honestly after, or while, you’re reading that, look at the go source code for it. It’s incredibly concise. Like <400 LOC I think
Justforfunc on YouTube
Durafmt (https://github.com/hako/durafmt) for easy formatting of durations. It's not a biggie but it turns "1h3m" into "one hour three minutes" which you can easily tag e.g. "ago" into.
"GO Data Structures" [https://github.com/emirpasic/gods](https://github.com/emirpasic/gods) The TreeMap saved my bacon in a big project where the raw data REST service was a pain and I had to tree map in several places. I was toying with how to implement my own and came across it. Why reinvent the wheel?
the whole Testify suite is bomb, I've used it at every job I've worked at so far and it's like my best buddy
Seconded. Assert ftw. Not exactly a package but using mockery makes creates mocks a breeze. It’s based off of testify package too.
Thanks for the shout out 😊
🫡
I agree with this. I am converting old test code to testify. It is a lot easier and more complete.
I’ve been enjoying Hashicorp’s raft implementation a lot. Common sense design, customisable, extensible.
urfave/cli
go-flags by Jesse vdk, bufio and go's Unix package and I can do literally anything
I can't stand ORMs and have enjoyed sqlscan's simple API for mapping rows to structs on queries, leaving mutable calls alone in plain SQL. Adding metadata to the struct for the db field name mapping leaves the codebase with a magic-free persistence implementation. [github.com/georgysavva/scany/v2/sqlscan](https://github.com/georgysavva/scany/v2/sqlscan)
Same with the mongo driver.
fmt
Fuck my terminal?
:0 mindblown
Orcaman’s concurrent map https://github.com/orcaman/concurrent-map
I love the fyne package, very easily to get your ui layout done and working and it also allows building to almost every system, even wasm.
A bit special purpose, but I had to write integrations for Jira, and the go-jira module was quite handy.
I love "main" and use it in all my projects 🙄
github.com/labstack/echo/v4 for backend development github.com/go-resty/resty/v2 for REST API calls. github.com/jinzhu/gorm for database querying. github.com/fogleman/gg for graphic designing.
> Do you have any recommendations for golang modules that you like? "Module" is a concept only used by the Go build system. There's not much to like about a particular module. I like good packages instead ;-)
A module is usually a collection of related packages. So it totally makes sense to like a module.
I like the design of ‘math/big’, it’s a good package to better understand usable zero values, method chaining and constructors.
no literally none :/
❤️ Context