Dear Future architect of some neat new technology to be someday posted on HN please do the following:
If you make anything with a UI, even a GUI stack, always include screenshots. If you make a programming language or programming framework / library, always include code samples!
Really show us nerds the bits we want to see right away, screenshots / code or even a video (fully optional, unless its some type of terminal shell or something where a video would illuminate things!) would sell it better. Many of us are working and don't yet have time to pull down everything to run it locally.
Honestly, even if its not open source, if you're selling a product, SHOW THE PRODUCT not just descriptions of the product.
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.
The repo doesn't say it, but the Author noted on the Gophers Slack #showandtell that the style was inspired by SwiftUI. That VStack example shows it quite well.
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!
Apparently a major dependency is "Fyne", which does show some screenshots on their page:
https://fyne.io/
If you make anything with a UI, even a GUI stack, always include screenshots. If you make a programming language or programming framework / library, always include code samples!
Really show us nerds the bits we want to see right away, screenshots / code or even a video (fully optional, unless its some type of terminal shell or something where a video would illuminate things!) would sell it better. Many of us are working and don't yet have time to pull down everything to run it locally.
Honestly, even if its not open source, if you're selling a product, SHOW THE PRODUCT not just descriptions of the product.
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??
m.div([m.h1("title"), m.p(["click", m.a({href:"..."}, "me")])])
you can do (taken from the page)
g.VStack(g.Text(...), g.HStack(...).Spacing(g.SpaceMD))
some people will like this style, others not.
I took a look at your recommendation, "gova"; it seems to be just getting started—keep up the good work!