mux VS Echo

Mir is a toolkit to develop RESTful API backend service like develop service of gRPC. It adapt some HTTP framework sush as Gin, Chi, Hertz, Echo, Iris, Fiber, Macaron, Mux, httprouter。

We will be using Gorilla Mux to create the APIs locally. Gorilla Mux implements a request router and dispatcher to match the incoming requests.

https://github.com/gorilla/mux/issues/659 Don't get me wrong, I appreciate the good intentions but why didn't you become a maintainer of the original project?

gorilla/mux

popular libraries looking for new maintainers and getting eventually archived ( https://github.com/gorilla/mux )

From the devs:

Initially found out about this via this issue thread here where they were looking for new maintainers.

The maintainer of Gorilla is in the process of dropping the project (he just doesn’t have enough time for it anymore) and is looking for new maintainers. A number of volunteers have replied to the issue but it seems like nobody has been chosen yet even though the call for new maintainers has been up for over a year.

According to maintainer requirements provided here, it's pretty obvious that it's quite hard to find new maintainers.

Mir is a toolkit to develop RESTful API backend service like develop service of gRPC. It adapt some HTTP framework sush as Gin, Chi, Hertz, Echo, Iris, Fiber, Macaron, Mux, httprouter。

I use Echo at my job, we have migrated from GoKit and is pretty good. https://echo.labstack.com

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

The little go book, Maybe that can help you a little bit, and then you could try echo High performance, extensible, minimalist Go web framework. 👌🏻 It has good documentation.

The project uses echo for serve as an http server, and we saved the config at the api/server.go file:

You should learn Echo and net http simultaneously, and I'll explain why. Go has a very high quality standard library which comes with a production quality web server and templating, and it has lightweight threads and concurrency primitives built into the language. So basically every library and framework builds on top of what is already there and as rule stuff integrates very well. I recommend Echo specifically because while there are lots of good frameworks, I think Echo is particularly good when it comes to documentation and code examples, i.e. beginner-friendly.

for me, Echo gives me that sense https://echo.labstack.com/

I'm thinking of recreating something like silverbullet using Vite, Svelte, Echo, Sqlite, anime, and web sockets. I'll host it in Docker on my mini server, access it via Tailscale and back it up with restic to Azure. I have some vague idea of building a web app that is both the editor and the app at the same time. Like a game where you build the game by playing the game, but with markdown and magic. Perfect side project fodder.

i prefer echo https://echo.labstack.com/ but from these two, i'd choose fiber