I reported a performance regression in the new experimental garbage collector planned for Go 1.25. It was a pretty beefy Hugo site with lots of very large JSON files processed with transform.Unmarshal and then used once. The new GC almost doubled the build times, and the culprit seem to come from a ...
As your test suite grows, you need ways to toggle certain kinds of tests on or off. Maybe
you want to enable snapshot tests, skip long-running integration tests, or switch
between real services and mocks. In every case, you’re really saying, “Run this test only if
X is true.”
So where does X come fr...
As the software we work on grows, the code tends to undergo various changes and refactorings. During this process, we might simply forget pieces of code that were once used but no longer make sense in the project, the infamous dead code. A very common example is when an API is deactivated, and only ...
Basically, I'm trying to figure out how I could allow a user to send a schedule in the cron syntax to some API, store it into the database and then send an email to them at that interval. The code is at gragorther/epigo. I'd use go-mail to send the mails.
I found stuff like River or Asynq to schedule tasks, but that is quite complex and I have absolutely no idea what the best way to implement it would be, so help with that is appreciated <3
When working with Go in an industrial context, I feel like dependency injection (DI) often
gets a bad rep because of DI frameworks. But DI as a technique is quite useful. It just
tends to get explained with too many OO jargons and triggers PTSD among those who came to Go
to escape GoF theology.
Dep...