Show HN: A Full-Stack Web Framework for Go • Hacker News Board

Re: Show HN: A Full-Stack Web Framework for Go

#101

Post by pphysch » Sun, May 15, 2022, 4:24 PM UTC

minism wrote: post #97

pphysch wrote: post #93

Earlier quoted context omitted.

That's fine, but you are making a trade off with productivity here.

You have to be careful because sometimes productivity is just an illusion caused by accruing technical debt that you have to then pay for in time later. With database abstractions you often pay back this debt once the app reaches even slight complexity and you need to spend a lot of time understanding, debugging and refactoring query flows.

Writing backend with raw SQL: $10

Writing backend with a rigid, verbose, mostly type-safe ORM: $5

Writing backend with a terse, expressive ORM: $2.50

Adding type annotations to the previous code: $1

Re: Show HN: A Full-Stack Web Framework for Go

#102

Post by abdouls » Mon, May 16, 2022, 6:52 PM UTC

As someone who uses (and loves) Laravel, this looks very promising! I've been looking for an alternative to Laravel in NodeJS but found nothing at the same level of it. Looking forward to using Bud in an upcoming project (will be a REST API backend in Go).

Re: Show HN: A Full-Stack Web Framework for Go

#103

Post by matthewmueller » Tue, May 17, 2022, 5:26 AM UTC

reddec wrote: post #88

First of all - great work, thanks. Will follow the progress. I have been working with Go professionally since 2015 and quite often it makes me feel frustrated due to lack of full-stack web frameworks. I was thinking to do something like your project, but with focus to full SSR/zero-js. Lucky me, you started it first . Maybe be in some things I will prefer different approach, however, your project already released (an…

@reddec, thanks for chiming in.

Having path helpers absolutely needs to happen, something like: https://guides.rubyonrails.org/routing.html#creating-paths-a.... I'll probably get custom routing up before that though because I want to make sure the design covers changes to routes.

There's a whole layer of generated JS/TS that will eventually be built out here.