i mean the whole thing is prob vibe coded. this was actually an exact thing i tinkered with when i first got a claude account. thought hey what if something easy like streamlit ergonomics for golang. gave up on that pretty quickly, it was one of those early "im gonna do something so big because im king of the world now" journeys that helped me learn where the limits of AI really is. with that said id love to see more gui developments in go. im actually not against AI helping speed this up, i just want people to be forthcoming about it. I need to know that they know what they're providing and what they're talking about.
but yeah i went thru the repo and the site and saw like one screenshot of like one component. i really dont think a guy who really actually cared about delivering something like this would kneecap its own success with a lack of screenshots for a GUI solution. that's beyond funny.
as for fyne.io, actually awesome to work with. but holy god it's so ugly, and they've worked themselves into a corner with how they wrote it. theres pr's and discussion ideas to give some users control over something like padding but it'll be a very painful bandaid to pull off and redo. hardcoded vals everywhere.
ive been kind of sitting back and waiting to see if AI was going to help someone who has more inspiration/drive/smarts than me launch something into the spotlight for go gui, but so far the biggest go gui successes still land in the web-technologies stack (wails). i look over at rust and see something like dioxus and i get sad. as far as desktop gui world goes, theres a glaring hole: i actually think aggrid (web tables) is my personal like bare minimum of what im expecting out of a table component. i havent really seen anything that matches it on the native app component front.
I once built a small utility using the "Fyne" framework; it was reasonably functional and made it very convenient to compile cross-platform executables (including for Android).
I took a look at your recommendation, "gova"; it seems to be just getting started—keep up the good work!
Looking forward to a Golang declarative framework.
My advice to the author: invest in rich multi-window support early on. It's easy not to, but you always need it in the end, and it's painful to retrofit.
I feel like there's a great cross-platform UI story to be told with Go, since cross compiling is so easy.
Intro code snippet has two buttons ("+" and "-") in an HStack. Expected them to be arranged horizontally but in the accompanying screenshot they're stacked vertically. Is that intentional?
18 comments
[ 0.21 ms ] story [ 146 ms ] threadApparently a major dependency is "Fyne", which does show some screenshots on their page:
https://fyne.io/
but yeah i went thru the repo and the site and saw like one screenshot of like one component. i really dont think a guy who really actually cared about delivering something like this would kneecap its own success with a lack of screenshots for a GUI solution. that's beyond funny.
as for fyne.io, actually awesome to work with. but holy god it's so ugly, and they've worked themselves into a corner with how they wrote it. theres pr's and discussion ideas to give some users control over something like padding but it'll be a very painful bandaid to pull off and redo. hardcoded vals everywhere.
ive been kind of sitting back and waiting to see if AI was going to help someone who has more inspiration/drive/smarts than me launch something into the spotlight for go gui, but so far the biggest go gui successes still land in the web-technologies stack (wails). i look over at rust and see something like dioxus and i get sad. as far as desktop gui world goes, theres a glaring hole: i actually think aggrid (web tables) is my personal like bare minimum of what im expecting out of a table component. i havent really seen anything that matches it on the native app component front.
I took a look at your recommendation, "gova"; it seems to be just getting started—keep up the good work!
Looking forward to a Golang declarative framework.
My advice to the author: invest in rich multi-window support early on. It's easy not to, but you always need it in the end, and it's painful to retrofit.
I feel like there's a great cross-platform UI story to be told with Go, since cross compiling is so easy.
I think the right mental model is that Gova is to Fyne like DaisyUI is to TailwindCSS??
https://github.com/mappu/miqt
With the compiler flags I tried, binary size was close to that of Gova:
https://github.com/mappu/miqt/issues/147#issuecomment-280033...
Qt bindings for Zig, using the same approach as MIQT:
https://github.com/rcalixte/libqt6zig