websocket
Minimal and idiomatic WebSocket library for Go (by coder)
errors
Simple error handling primitives (by pkg)
| websocket | errors | |
|---|---|---|
| 18 | 31 | |
| 4,568 | 7,511 | |
| 1.7% | - | |
| 5.7 | 0.2 | |
| 18 days ago | almost 4 years ago | |
| Go | Go | |
| ISC License | BSD 2-clause "Simplified" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
websocket
Posts with mentions or reviews of websocket.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-08-26.
-
aria - Event Driven websocket framework
Aria is a lightweight, event-driven WebSocket framework for Go. It is inspired by olahol/melody and built on top of coder/websocket.
-
Lies we tell ourselves to keep using Golang
As a regular Go user, I agree with this take. Though the tools exist, error wrapping and checking (with errors.Is and so on) is actually pretty rare in my experience.
Positive example of good and appropriate usage here: https://github.com/coder/websocket/blob/master/internal/exam...
-
Building Simple Real-Time System Monitor using Go, HTMX, and Web Socket
Websocket
-
Possible frameworks/languages for a web/mobile application
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
-
Websocket memory usage
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.
- I don't understand these lines of code in Gorilla websocket example
- Websockets with golang
-
Portal - a modern file transfer utility 🌌✨
nhooyr/websocket, shollz/pake, charmbracelet/bubbles, charmbracelet/bubbletea, charmbracelet/lipgloss, muesli/reflow, klauspost/pgzip and many, many more.
- Is there an alternative to gorilla websocket?
-
Gorilla/websocket or Melody?
link: https://github.com/nhooyr/websocket
errors
Posts with mentions or reviews of errors.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-11-26.
-
Lies we tell ourselves to keep using Golang
https://github.com/pkg/errors provides stack traces support. This unfortunately did not get included in the Go1.13 release when error wrapping was introduced.
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
-
Cant wait for less verbose error handling
The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.
- Error handling and serializing
-
isse for go path in neovim
I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`
-
What am I supposed to be doing with errors?
Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors
-
Go error handling is not verbose but the error handling itself.
Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.
-
How to wrap the error best?
Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.
- mdobak/go-xerrors: Yet another error handling library.
-
Getting at the type of error after it has been wrapped with errors.Wrap
Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".
What are some alternatives?
When comparing websocket and errors you can also consider the following projects:
nbio - Pure Go 1000k+ connections solution, support tls/http1.x/websocket and basically compatible with net/http, with high-performance and low memory cost, non-blocking, event-driven, easy-to-use.
go-multierror - A Go (golang) package for representing a list of errors as a single error.
ws - Tiny WebSocket library for Go.
errorx - A comprehensive error handling library for Go
go-quilljs-delta
go-chat-bot - IRC, Slack, Telegram and RocketChat bot written in go