Maintained?

[bscott]

Is this framework still maintained?

It seems that issue management and acceptance of PRs have stalled.

[hoachnt]

Yes, it's sad

[matthewmueller]

Hey sorry for the delay! It's true that development has paused for now.

The challenges themselves deserve a blog post, but the TL;DR is that I ran into some issues with generating so much code while still giving users the flexibility to swap out pieces of that generated code. It was mostly UX issues around the package naming and API discovery, honestly.

What aspects of Bud were most exciting to you? One thing that I've been doing semi-privately is breaking off chunks of Bud and making them more legit. For example, some of the frontend code is now a completely independent, well-tested, feature-rich tool. I think there's an opportunity to take those isolated tools and merge them back into Bud at some point in the future.

[hoachnt]

I'm glad you're still in touch. Overall, the project is very interesting to me, I hope that everything will get better soon and the project will continue to develop.

…

On Wed, May 22, 2024 at 10:31 AM Matt Mueller ***@***.***> wrote: Hey sorry for the delay! It's true that development has paused for now. The challenges themselves deserve a blog post, but the TL;DR is that I ran into some challenges with generating so much code while still giving users the flexibility to swap out pieces of that code. It was mostly around the package naming honestly. What aspects of Bud were most exciting to you? One thing that I've been doing semi-privately is breaking off chunks of Bud and making them more legit. For example, the frontend server is now a completely independent tool. I think there's an opportunity to take those isolated tools and merge them back into Bud at some point in the future. — Reply to this email directly, view it on GitHub <#416 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV4FFN5JEAB3EVPG2IXWK5DZDQGRNAVCNFSM6AAAAABFPYGJ3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRTHAYDENJRHE> . You are receiving this because you commented.Message ID: ***@***.***>

[yanickrochon]

I stumbled across this project from this post. If this project could support Vue.js, Solid, etc. and come with built-in user authentication, then I believe this would help the momentum.

I came here because I am exploring Go. Not sure if am a good fit as a contributor, but this all look quite promising!

[cggonzal]

An ORM with auth and migrations support would really tie everything together and speed up development of standard CRUD apps.

Migrations was one of the things that was a pain to get into Django but really solidified the dev experience.

ORM's with good tooling are a pain in general but they're one of those things that speed up development so much that you can go from teams of 10 to teams of 1.

Edit: It looks like these are on the roadmap but getting them done would be no small feat. However, the value-add would be phenomenal, imo.

[Quephara]

found this through a youtube reccomendation. only to notice the age of commits and the development focus seeming to be more on the duo repository.

for auth, id wager goth is good. i dont know what orm to use though

[Wishmater]

I love the idea of being able to just call svelte directly from the controller, with the data I got from go code. I love go for servers, but the templates is the worst part by far. Just being able to use svelte (or any other framework) instead of the go templates is huge. The bud project is awesome, but way too ambitious in my opinion, would be excited to see it maybe broken down into smaller packages, specially the part for interfacing with JS frontends.

[neilyoung]

Stonedead... You should consider to archieve that