Thanks for watching! 🙌 Here's how to dive deeper into GOAT Stack: 1⃣ Get started quickly: goat.morethancoder.com for our comprehensive quickstart guide 2⃣ Join our community and newsletter: morethancoder.com for more Go and web dev tips Got questions about GOAT Stack? Drop them in the comments below! Don't forget to like and subscribe for more content on Go, web development, and cutting-edge tech stacks. 🚀
I've been working on a "democracy sim" using this stack along with EdgeDB. Using two alpine plugins: alpine-ajax and alpine-intersect, I was able to get infinite scroll working with multiple horizontal lists for the past and current leaders and legislators of different places. Loading spinner included. Tailwind + alpine + templ really allows you to get like 90% functionality of React with no wacky build steps. Very productive stack if your project is primarily DB/backend driven.
go templ is a liability. do your research, if you agree, then drop it, use the standard templating engine of go + htmx instead and for the db, go with sqlite and you have the perfect "stack". people are sleeping on sqlite and people are too snobby to properly grasp htmx's value and utility. go + htmx + alpinejs + tailwindcss + sqlite = solid you dont need anything else. however, it all comes down to preference. in the end, all the user sees is html + css, with some js in the background for functionality. how you produce that is a personal preference. try out multiple ways and pick that which tastes best to you.
I really want to like templ. In my experience playing with it so far is that its fine for static components, but once you have to start creating dynamic content, more specifically, dynamic strings, it turns into a huge mess of fmt.Sprintf() everywhere. Dynamic urls are even worse with the string(templ.SareURL(fmt.Sprintf("/post/%d/edit", Post.Id))). God forbid you have to dump something into alpinejs.
I agree. For me the really pain comes in dumping to alpine js. Its such a maintainability nightmare, i might as well have just done a spa to begin with
Thanks for watching! 🙌 Here's how to dive deeper into GOAT Stack:
1⃣ Get started quickly: goat.morethancoder.com for our comprehensive quickstart guide
2⃣ Join our community and newsletter: morethancoder.com for more Go and web dev tips
Got questions about GOAT Stack? Drop them in the comments below!
Don't forget to like and subscribe for more content on Go, web development, and cutting-edge tech stacks. 🚀
I would like to see a complete project made with this, not just singular items
I've been working on a "democracy sim" using this stack along with EdgeDB. Using two alpine plugins: alpine-ajax and alpine-intersect, I was able to get infinite scroll working with multiple horizontal lists for the past and current leaders and legislators of different places. Loading spinner included. Tailwind + alpine + templ really allows you to get like 90% functionality of React with no wacky build steps.
Very productive stack if your project is primarily DB/backend driven.
@@benbowers3613 wow 😳
@@benbowers3613 that, I would like a showcase of that. Because singular items in isolation do nothing in convincing me I should test this out
Me too
Your work is fantastic. I'll test it here for sure. Congratulations and thanks for sharing this stack.❤
Very nice. Will try it out this weekend!
Please do!
I'have use this before and its great! but the setup (DX) make me hesitant to use it again
You could also add `air` to live reload you golang app
I get live reloading using CLI tools like entr or fswatch.
I think the stack already use Vite for this
Awesome 🎉
Thanks for the video!
Greetings from Brazil 👋🇧🇷
It looks impressive! Thanks for sharing
go templ is a liability.
do your research, if you agree, then drop it, use the standard templating engine of go + htmx instead and for the db, go with sqlite and you have the perfect "stack".
people are sleeping on sqlite and people are too snobby to properly grasp htmx's value and utility.
go + htmx + alpinejs + tailwindcss + sqlite = solid
you dont need anything else.
however, it all comes down to preference. in the end, all the user sees is html + css, with some js in the background for functionality.
how you produce that is a personal preference.
try out multiple ways and pick that which tastes best to you.
How is htmx relevant if this is supposed to be a frontend stack? Htmx is server-side after all
@@katm9877 my sweet summer child, you know not what you are talking about.
what on earth are you talking about?
templ is pre-compiled, no more of a liability than Go itself is
Do you have some public projects that we could look at using go + htmx + sqlite that you could link to to learn more about what you are saying?
Does this stack use HTMX?
Hi. What are you using for the pretty content you are showing in this video? Possibly something like revealjs?
Nothing fancy just some Figma slides :)
Do you want to know my stack??? Its just a static html file with hello world
Cool
The amount of STACKS I've seen is getting JS libraries levels of absurd 🤣
Lol FARM stack to GOAT stack
I really want to like templ. In my experience playing with it so far is that its fine for static components, but once you have to start creating dynamic content, more specifically, dynamic strings, it turns into a huge mess of fmt.Sprintf() everywhere.
Dynamic urls are even worse with the string(templ.SareURL(fmt.Sprintf("/post/%d/edit", Post.Id))). God forbid you have to dump something into alpinejs.
I do it all the time yes you need to use fmt.sprintf most of the time but you don't necessarily create a mess.
I agree. For me the really pain comes in dumping to alpine js. Its such a maintainability nightmare, i might as well have just done a spa to begin with