What's your development env?

[vitezprchal]

Hey, I'm finding my current development environment for go and go templ to be really slow.
I'm currently using air, gin, templ, tailwind and thats it.
Could you share what setup you're using that might help speed things up?

[nexovec]

Which part of it do you find slow?

[amoghyermalkar123]

@vitezprchal if you are referring to the slowness of the dev process itself, (like creating the project, building assets, reloading things) you can use a template like so - https://github.com/amoghyermalkar123/templ-quickstart
this is a fork ive added a makefile automation to.

[vitezprchal]

Specifically, when I recompile, my current stack using air & gin takes around ~2000ms just to refresh. Any suggestions would be appreciated

[joerdav]

Some additional information may help in this scenario please. If you have a repo that can be cloned we can see if the slow reload is due to the configuration or not. If this isn't possible then it could be useful for you to record a screen capture of the terminal as it reloads (with the -v flag enabled on any templ commands).

[gregmulvaney]

Go is a compiled language. Changes require recompiling the binary which isn't as quick as a hot reload on an interpreted language like JS

[vitezprchal]

Yes I'm aware it is compiled language I was thinking of making templ binding for javascript just for dev purposes

[jhelberg]

GNU emacs with LSP and tree-sitter works great. For building it's generate-lines and a makefile.

[nexovec]

I use helix for editing, and I also use air for hot reloading, like you all do. I develop in a container, it allows me to stage a network environment of the application and be a part of it, it's also a nice replicable environment. I'd much like to go with an embedded database like SQLite, because then I could run everything locally, but postgres is just so much more powerful.

A thing that can help with build time is to use

cmd = "go build -o ./executable -gcflags '-N -l'" # Unoptimized build
bin = "executable"

in your .air.toml.