websocket VS melody

In my experience Go has been relatively approachable for people that are good at PHP. It has a great standard library and a pretty solid ecosystem, though frameworks aren’t as popular in Go. There are some well regarded libraries for things like WebRTC via https://github.com/pion/webrtc WebSicket via https://github.com/nhooyr/websocket

Also take a look at https://github.com/nhooyr/websocket - which is a good ws library, but I don't have anything specific about its memory usage per connection. But from what I see it will be somewhat similar to x/net/websocket.

nhooyr/websocket, shollz/pake, charmbracelet/bubbles, charmbracelet/bubbletea, charmbracelet/lipgloss, muesli/reflow, klauspost/pgzip and many, many more.

link: https://github.com/nhooyr/websocket

There's https://github.com/gobwas/ws and https://github.com/nhooyr/websocket but neither have seen a commit in over a year

The last time I was using websockets, I found https://github.com/gobwas/ws to be a huge improvement over Gorilla, but I haven't been looking recently, and perhaps Gorilla was able to shed some of its bloat and improve API and performance since then.

I just recently started using melody (https://github.com/olahol/melody), which claims to be like gorilla websockets. I found it pretty quick to understand, but I haven't used it for anything that complicated. Has anyone used both melody and gobwas/ws? I'm mostly interested in ergonomics, not performance.

I recommend https://github.com/olahol/melody It is based on gorilla websocket but abstracts the tedious part. I have used it in my distributed chat side project

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.

I like github.com/olahol/melody which is based on gorilla/webscocket very much and use it in some of my projects which do not have too many online connections.