air VS delve

Note: Make sure you have Air installed. See 👉 How to install Air

The last problem for now is a hot reload module. Whenever we create a fiber app we don't have any change listener by default. If fiber has this already and I do not know about it then forgive me for that I am relatively new to this. If you know anything about this, let me know in the comments. To solve this problem I figured out to include air in the project.

We will use https://github.com/air-verse/air to do live reloading for us.

Ever since I have been making APIs there was always a simple way to enable hot reloading. It is easy in Go too, you just have to use air. It so simple, just write air and you have hot reloading. Now you may ask the question that if it's so great what this post is for?

Air is another library that enables hot reloading in Go applications. To use it, install it on your machine using the command below:

To enable live reloading in Go we will checkout the command tool, Air - Live reload for Go apps.

☁️ Repositório do Air

This is made possible thanks to the Air tool, which now comes with every project you create. The configuration is as follows:

In this post I'll elaborate the powerful combination of Emacs, Delve, and dape. Together, these tools create a debugging experience that mimics (and often surpasses) traditional IDEs, while preserving the flexibility and extensibility that Emacs is famous for.

Delve: Popular debugger for Go.

Edit air.toml [[go build]] command to: - all: flags should be applied to all packages in build packages - -N: disabled optimisations to ensure generated code closer to source code for easier debugging - -l: disables inlining optimisation where small functions are expanded in place to reduce overhead of function calls, making it easier for debugging - Reasoning from Delve Reference

Delve: A debugger for the Go programming language.

At a recent job, we had slightly different containers for local dev; our backend containers (for a Go app) had Air [1] installed for live reloading, plus Delve [2] running inside the container for VS Code's debugger to connect to. We also had a frontend container for local dev, which didn't get deployed as a container, just as static files.

[1] https://github.com/cosmtrek/air

[2] https://github.com/go-delve/delve/

https://github.com/go-delve/delve/releases/tag/v1.21.2 Thanks Derek and the rest of the team for helping us to debug in a normal way!

My employer has a commercial solution for this but Delve does supports `rr` traces natively for this purpose, which gives a complete open-source solution (https://github.com/go-delve/delve/blob/master/Documentation/usage/dlv_replay.md).