Ghostly is a simple, lightweight, and fast full-stack framework for Golang

Slightly off-topic question. What are you using to do the rendering and validation of forms in a "Django like" way in Go? I have a half-backed system build using the ideas coming from Django but I wonder if something a bit more robust exists.

My impression is that more and more people are just submitting forms a JSON through an heavy weight app to an API end-point and less people are using forms "the old way". So, if some "old people" have some pointers for another "CGI old dev", I would really enjoy them!

Are there any examples of things built with Ghostly?

Looks good, will have to try it. What are the competitors to this? I ask because I want to do my next side project in go.

I’m using Echo which work pretty good with SPA like Vue 3.

Wish I could find job opportunity to utilise these.

I work with go for years but never used a fw. At the beginning when i came from php, i looked for fw because that was how things were done. But once i let go of that idea and started making things by hand i never looked back. Go really does not need a framework. Sooner or later it starts to limit you. For example i used grpc a lot in the past but came to realize it was hindrance and now i just use proto files to define schemas and generate the structs but that's is all it does. Everything else is hand-made. I even moved away from SQL abstraction and just use sql and directly. Again, sooner or later there will be some limitation that will bother you and so it is just not worth it. And being able to tailor-made every part of the application for its desired purpose is priceless.

The readme doesn't seem to mention or list what libraries this depends on, it has chi and jet at least based on the structs section.

Given this "framework" is predominantly a collection of other people's (usually apache/mit) work, where is the BOM/licence text including all of the dependencies?

And why has the author attempted to licence their likely sub 100 lines of glue code under the GPL?

I don't see the point in using something like this which is basically a prefilled go.mod with some other files with a pretty stock organization.

I've used Pagoda (https://github.com/mikestefanello/pagoda) in the past which makes a show of displaying its nature as a wrapper around a bunch of community libraries, and is documented as such. They also make effort to document the interfaces for each component so you could easily replace them with your own implementations to avoid getting stuck due to the "framework". This is my preferred approach for all of these "starters" now since using pagoda.

I'll be honest, the "full documentation" just being generated API docs isn't great.

Just show me how you use it, damnit.

This having the GPL license is an interesting choice. If I understand licenses correctly (I am not a lawyer), integrating this into your code, will instantly cause your website's source code to become open source.

That seems like a non-starter for almost every major usage, to me.

It doesn't even explain it's a web(?) framework. Just "full-stack framework".

I'm not sure what the value of a "framework" is in Go.

What's the best way to learn Go these days? Any recommended books?

Are you serious, frameworks similar to Iris gone? And we now have to use this?

Here we go again, yet another wannabe code it like it's Ruby or Python. Frameworks are useless in Go!