2026-10-07 20:26 UTC
@jsecure@skyhaven.social I miss Go, and there is a valid argument that the language I'm working on is in a similar space (compiled language that's explicitly friendly to people from a scripting background).
I have found in the last couple years, working on other people's Go code tends to be a bit fraught. This codebase seems pretty alright, at least, but with no good way to test changes to the majority of the code. I had to lay down and I may not get to do more code today. But the next steps definitely involve enhancing the Madon test suite to be able to exercise it against a mock of a real Mastodon API service.
Replies (1)
-
@jsecure@skyhaven.social 2026-10-07 20:34
@MaddieM4@raphus.social Yes I think testing is so crucial for any Go codebase. I use really nice Ginkgo / gomega tests which describe what is happening ie: When("the user enters some stuff and", func() { When("the users input is invalid and", func() { When("the validator spots the issue", func() { It("should output an error", func() { I find this a lot more intuitive than the bare tests which come with the core libraries. Go is very opinionated and idiomatic so it kind of keeps codebases looking similar but when tests are easy to follow it can really help readability.