Seattle crew - we're hosting none other than @sullyE64 and @aquarian this Saturday along with a brand new Void Acoustics sound system, it's gonna be very good, do not miss, etc🫠🫠
@atomly wouldn't recommend abusing empty interfaces like this, though, still better to use models. Maybe that's rigid, i dunno, but it does ensure that other APIs don't push breaking changes without people (specifically: you) complaining like crazy
@atomly alternatively, you can also chuck JSON (or parts of it) into an empty interface. You'll still be casting later on but it won't be as verbose as using Go generics go.dev/tour/methods/14
@atomly I do most of my dev work in TypeScript these days, so I get your critique around arrow functions and boilerplate and all of this. However, when you've got a team of devs with really varying skill levels, I do like having some strict contracts in place, and Go is awesome for that
@atomly So for example, instead of making generic types (I never use Go generics, btw), Go is best when using structs liberally. Example of a decent graph traversal: github.com/0xAX/go-algori…