I find it kinda odd that github.com/gorilla/websocket, which is deprecated and the repo is in archive mode, is still the most popular library for websockets.
Case in point: go.elara.ws/go-lemmy
I’m not saying this is inherently bad, I just wonder why that is.
I guess the most common last words are “How hard could it be?”, but why is nobody rolling their own?
I guess it’s because
gorilla/websockethas had a really big mindshare for a very long time. and no project has had time to catch up and/or provide “reliable” hints that they will maintain that new project for a sizeable long time.“the devil you know” and “the technical debt you know”…
Yes, and unless WS suddenly change, it’ll likely keep working for a long time.
The reason I’m skittish is because there might be undiscovered security issues, and it feels like a huge chunk of the community just don’t care.
My hunch would be that so much boilerplate already exists, and golang is so extremely popular, that a lot of it is being pulled into tutorials, samples and new projects. If it already exists there, I doubt the many users even check the repo.
Yeah, I think that might be why it keeps spreading even after being deprecated.
It might be beneficial to gather together a team to maintain a fork …
