dont parse templates in runtime, parse them during init instead
@FloWoelki
5 ай бұрын
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
5 ай бұрын
@@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
5 ай бұрын
@@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.
@phat80
3 күн бұрын
Don’t see the reason to use htmx. All what was shown can be easily made with simple JS with no need to learn htmx syntax.
@HarmonicaTool
2 ай бұрын
Thank you and please. Please make more videos on how to use Golang and htmx for usefull webapps or even just to use htmx instead of a local GUI. It is hard to find a beginner friendly route to start.
@siya.abc123
5 ай бұрын
All htmx tutorials are simple. Why no one wants to show how to build production grade apps? Styling, components etc
@FloWoelki
5 ай бұрын
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
4 ай бұрын
@@FloWoelki Yes that would be awesome
@GreatTaiwan
Ай бұрын
@@FloWoelki none of what you mentioned is actually related to Go or HTMX this is still a ToDo with better devOps tools around it something other than ToDo I think is required, look at making a medical image reading project, a game maybe ...etc something along the lines of having many domains and components to see how this can actually scale or will be complete rewrite
@theseangle
13 күн бұрын
@@GreatTaiwan todo is the perfect app actually. It can have authorization, multiple views (todo list, details view, authorization pages, profile pages), protected routes, utilize HTTP headers, persistence via database, Redis, dynamic assets like images (-> S3 buckets), mounting an SPA to a part of a specific heavily interactive page, I could go on and on. - Medical imaging? Nobody would watch that. - Game? Nothing relevant to htmx/go, just Javascript and a lot of programming patterns. - An over-engineered to-do app? Heck yeah!
@theseangle
13 күн бұрын
@@FloWoelkiI hope you read my reply to @GreatTaiwan
@merfkit
5 ай бұрын
Thanks, very good and understandable guide👍Hope to see more rust/go videos in the future
@FloWoelki
5 ай бұрын
thank you so much! there will be definitely more content about Rust and Go!
@gelismissuriyeli4440
2 ай бұрын
Thank you for this well-made video. My question is, would it be possible to still inject the data in the templates (that easy) if we follow the `Separation of Concern` paradigm and have the BE and FE apps run in separate environments say.. Docker containers for example?
@DougLopes
Ай бұрын
Nice video, just the abbreviated variable names make me nuts.🤣🤣🤣
@FloWoelki
Ай бұрын
Fair point :D and thank you!
@kingsgambit9284
5 ай бұрын
Wow 😮
@sergeiudison6534
26 күн бұрын
Thank you very much!❤
@FloWoelki
26 күн бұрын
You're welcome 😊
@grimonce
Ай бұрын
Had me until this != font heresy.
@FloWoelki
Ай бұрын
Fair point :D I've also removed this for my personal use and future videos.
@theseangle
13 күн бұрын
It's called ligatures
@grimonce
13 күн бұрын
@@theseangle not sure if that's the case. I'd call it inverse ligature or something between. There are actually two signs that are required by the language formal syntax, they are not "joined", only displayed as such to the user of the plugin. While a ligature is actaully a joint sign... so no? Not sure what you're aiming at anyway.
@LourensRolograaf
Ай бұрын
On 8:12 it says "GO = HTMX Demo" and "{{.Message}}" on my localhost:8080 page. Something changed since I am already using Go version 1.23 maybe? cannot find the mistake in my code
Пікірлер: 26