bud VS sqlc

Hit me up if you have a longer time horizon and want to give https://github.com/livebud/bud a shot!

There is https://gobuffalo.io/ and there is https://github.com/livebud/bud. Both are interesting approaches, but sadly, without real business interest from the community. See, 90% of what makes Laravel Laravel (or Rails Rails) is business adoption. And, as you will sadly find out, the business adoption for traditional Web applications is exactly zero. If you don't want to make the same mistake as I did, and spend 3 years of your life searching for it, do as the others advised - just use the tools and frameworks that have already been built to solve the problem you need.

Awesome!

This would be such a game-changer for server-side rendering Javascript in Go with V8.

I'd love to integrate this into Bud[1].

[1] https://github.com/livebud/bud

I've also been seeing updates on this project, which is kind of preferring Svelte https://github.com/livebud/bud

https://github.com/livebud/bud - similar idea, but uses Svelte (a JS framework) to do the front end stuff. It’s smart enough to render the JS stuff on the server when possible, so you end up with the best of both worlds.

https://github.com/livebud/bud this framework is achieving SSR in go. Not Vue specifically last I saw, but maybe you can draw inspiration from what they did https://www.reddit.com/r/golang/comments/uoxocj/bud_the_fullstack_web_framework_for_go_developers/i8ke92h/?utm_source=reddit&utm_medium=web2x&context=3

See https://github.com/livebud/bud to learn more.

An open-source GoLang project also took the same approach, livebud/bud.

It's not that I am not able to develop APIs, but being an indie dev makes me seek proper full-stack frameworks, so I have been seeking some frameworks, Rails is one of them. I have pretty confidently learnt Rails 7. But another GoLang framework popped up, which is Bud (aka LiveBud GoLang).

Ah cool! I'd like to support Vue through plugins rather than bake it in. There's an open discussion here on Vue support: https://github.com/livebud/bud/discussions/39

I came across this yesterday for golang: https://sqlc.dev which is somewhat like what you want, maybe.

Not sure it allows you to parameterize table names but the basic idea is codegen from sql queries so you are working with go code (autocompletion etc).

Agreed, but tools like https://sqlc.dev, which I mention in the article, are a good trade-off that allows you to have verified, testable, SQL in your code.

sqlc is not strictly a conventional ORM. It offers a unique approach by generating Go code from SQL queries. This allows developers to write SQL, which sqlc then converts into type-safe Go code, reducing the boilerplate significantly. It ensures that your queries are syntactically correct and type-safe. sqlc is ideal for those who prefer writing SQL and are looking for an efficient way to integrate it into a Go application.

I was browsing awesome-go for ideas on how to setup my data access layer when I stumbled on sqlc. It seemed like a great option. Code generation is a strategy often used in the Go ecosystem and making my queries safe at compile time was an idea I really liked. Knex was great, but it required of me that I test thoroughly my queries at runtime and that I sanitize my query results to ensure type safety within my application.

Now, we are going to generate the code. For this purpose, we are going to use sqlc.

https://github.com/sqlc-dev/sqlc — for use with //go:generate