Community highlights
Who's Hiring - October 2025
Small Projects - September 30, 2025
Frequently Asked Questions
Hey folks, in your opinion what's the best tool to build GUI in Go?
My current choice is Wails and it works well 99% of the time, but now that Topaz Labs decide to shift their products from one time payment to subscription, I decided to create an open source version of their products, starting with Topaz Photo AI (I know it's ambitious, but I think it can be done).
However, AI apps are usually resource intensive and would like my app to have a more native look, instead of a web look. Is there anything you would recommend in this case?


god i hate this. every config, every helper must be generic. "what if we'll use it for–" no mate: 1. you won't 2. you've made a simple type implement a redundant interface so that you can call a helper function inside another helper function and 3. this function you've written doesn't even need to use the interface as a constraint, it could just take an interface directly.
i keep having to review shit code where they write a 6 line helper to avoid anif err != nil
(now the call site's 4 lines, good riddance god help). it's three against one and i'm losing control and i'm pulling my hair out trying to understand wtf they want to do and the only way to convince them we can do without is if i rewrite what they did from scratch and let them see for themselves it's just better without the shit load of abstraction and generic abuse.
don't even get me started on the accompanying AI slop that comes with that.
how can i convince my colleagues to design minimal composable abstractions which actually fit in the current codebase and not dump their overly engineered yet barely thought out ideas into each file as if it was an append only log? i'm tired of rewriting whatever they do in 30-50% less lines of code and achieving the same thing with more clarity and extensibility. i wish numbers were hyperbolic. in fact, they're underestimating.