flamingo VS websocket

I'm aware of: - A k8s cronjob shelling out to the terraform CLI - flamingo -> Flux -> weaveworks Terraform controller - Terraform cloud operator - Crossplane's terraform provider

Weave's TF-Controller, which also has fewer bugs, much better adoption, and it looks like it's actually being developed by someone. But requires a weird argocd <-> flux interop boilerplate. It's a "controller for flux" and not a Kubernetes controller, and I don't really get such ambiguous targeting , but meh...

What I can say is that if you will use Gorilla Websocket (https://github.com/gorilla/websocket) (it's archived now unfortunately, but still super robust) - then you can go to sth like 15-20kb per connection - see https://github.com/FZambia/go_websocket_memory - to achieve this you need to reduce read buffer size, reuse write buffers, use goroutine after hijacking connection (following chat example in Gorilla WebSocket repo).

No Bugs? https://github.com/gorilla/websocket/issues Even if that were true at the time of stoping development, "No bugs" is something that can never be said for any software. I really wish this community stopped recomending to use abandoned libraries if only for the potential Security issues. A not maintained Library is a very lucrative target for vulnerability hunting.

The Gorilla WebSocket License says:

We'll be using WebSocket library: "github.com/gorilla/websocket" ❣️

package github.com/gorilla/websocket is not a main package

As for Websockets, (https://github.com/gorilla/websocket) it uses ws.NextReader() to handle heavy loads of connections.

I'm looking to build a game server that uses web sockets to communicate with clients, I've looked into some of the libraries and the main ones seem to be gorilla websockets and melody.

If this is what your import looks like "github.com/gorilla/websocket" that's wrong it should be just "github.com/gorilla/websocket"