Why HTMX and Golang? The answer might surprise you...

HTMX and Go is such a beautiful and simple combination. This video covers a basic web server built with HTMX and Golang. If you want to learn Golang in 15 minutes, feel free to check out this video here: • Go from Zero to Hero: ...
📝 Description
In this video, we explore the beautiful and simplistic solution that Golang and HTMX offer for full-stack development. Together, we build a small project using these two technologies and discuss why they form such a great combination. From discussing why HTMX is so popular in the Go community to building an example web server, this video is packed with insightful information. Whether you're new to the software engineering world or a seasoned professional, there's something to learn.
⏳ Timestamps:
00:00 - Introduction
00:28 - Why HTMX and Golang is powerful?
01:18 - Building the Web Server
11:22 - Outro
👋 Hey there!
If you are new to this channel: Hey 👋 my name is Flo and I am a professional software engineer with a passion for coding in Golang, TypeScript, JavaScript, and Rust. This channel is where I share that passion and dive into the exciting world of software engineering. Plus, I love using Emojis and paper-based animations (so have a look for that, if you want to find my videos).
📨 Support and Connect!
Buy me a coffee: www.buymeacoffee.com/florianw...
Become a member: / @flowoelki
Discord: / discord
Instagram: / flowydev
LinkedIn: / florian-woelki
TikTok: / florianwoelki
GitHub: github.com/FlorianWoelki
#golang #go #htmx

[@iskariotski]

dont parse templates in runtime, parse them during init instead

[@FloWoelki]

yeah I 100% agree. it was a mistake on my end! to parse it over and over again whenever a request was made is just not efficient. but this was just a simple demonstration of using HTMX with Go. edit: I've pinned your comment so that everyone can see it :)

[@ransomware9086]

@@FloWoelki no. don't use init, since it adds a side effect to import behaviour. create your own init routine and do it in there

[@FloWoelki]

@@ransomware9086 thank you for the comment. I think parsing the template in the request is always bad for performance, it's alright for dev purposes. but, for production, the template should be fixed and only the data should change.

[@merfkit]

Thanks, very good and understandable guide👍Hope to see more rust/go videos in the future

[@FloWoelki]

thank you so much! there will be definitely more content about Rust and Go!

[@kingsgambit9284]

Wow 😮

[@buddy.abc123]

All htmx tutorials are simple. Why no one wants to show how to build production grade apps? Styling, components etc

[@FloWoelki]

I could do it ;) do you have anything specific in mind? like creating a todo list and then making it production-ready and deploying it (I think dockerising the application should be feasible enough?)?

[@nanonkay5669]

@@FloWoelki Yes that would be awesome