mux VS Gin

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.

Correct example is here. But instead I suggest you just use unsafe.String and unsafe.Slice since runtime headers are deprecated anyway. You can find example here.

unsafe.Slice and unsafe.String came with Go 1.20 as I remember I will add that part, what do you think about Gin 1.19 bytesconv implementation? Is there a similar issue maybe?

The back-end is going to be written in Golang, using a [Gin](https://github.com/gin-gonic/gin), [Gorm](https://gorm.io/), and a [Postgres](https://www.postgresql.org/) DB, so bonus points if you are familiar with Go!

I found this article about someone who evaluated Gorilla Mux replacements and chose Chi, which may be helpful. FWIW I did some of my own investigation and I'm leaning towards Gin, since it's more performant which is a factor for my current usecase.

Specifically for nhooyr/websocket, I can see that one of the issues raised in the PRs is meant to address CVE-2020-28483 that affects github.com/gin-gonic/gin . If I run govulncheck on nhooyr/websocket, it does not list it as been vulnerable to that particular issue. And yes that particular CVE exists in its database; https://pkg.go.dev/vuln/GO-2021-0052

Our main function in this service is very simple. There is a single POST endpoint to receive stats. I'm using Gin framework for routing here.

To learn more about Gin framework, you can check out the docs here

Disclaimer: I'm not a frontend dev, I'm not a mobile app coder and I didn't really want to do anything. But I happen to code fairly often in Go, and so I figured the type table was really just a big map of values (either 0, 0.5, 1 or 2) tying one type to all other types... Could I maybe get away with a backend app that would handle it? Surely not... But I had recently noticed the Gin HTTP framework and it seemed fairly easy to use.