meta: Status update and v2.0.0 holy grail requests

[nhooyr]

I've been gone from this library for a while now but I'm back now. I'm going to be working on it full time till the end of the year.

I'm going to start by fixing all the minor outstanding issues and adding all currently requested features without breaking any backwards compatibility. I want v1 of this library to be rock solid and feature complete to the extent it makes sense.

But after that, I want to work on a v2 where I change the API a bit here and there to entirely perfect it. I don't anticipate major changes as I quite like the API. It has stood the test of time. My main irk with the API is that's a little too constrained. I don't think it should be necessary to sacrifice any performance whatsoever in using my library vs gorilla or gobwas.

I want the comparison to say there is absolutely no rational reason to use any other library except this one if you're writing WebSockets with Go except for stability (though v1 of my library is quite widely used now too though still about 10x less than Gorilla).

The aim is to strike an even better balance between performance and being idiomatic. I have a few ideas but nothing's finalized. I'm also a massively better engineer than I was in 2018 (5 years ago) so there's lots of code quality to improve too.

If anyone has suggestions, please share them here. Ideally those rooted in the long term use of my library. As I fix up v1 and my ideas become very concrete, I'll publish them here first to get feedback before I implement.

cc @tailscale @coder

[nhooyr]

v1 will be maintained alongside v2 for as long as it's feasible. For security issues I'd say at least 5 years if not more. After my push these next few months, I don't expect it'll need much maintenance work except for occasional minor fixes.

I know it sounds rich to promise such a long timeline given my very recent 2 year absence but my absence had good reasons that will not repeat.

[nhooyr]

Ooo, I'll maintain v1 indefinitely. I'll just reimplement it in terms of v2.

[s0kil]

@nhooyr Great!, We are using the lib in prod, thanks for your work.

[emersion]

Thanks a lot for your dedication!

[balog-avaya]

@nhooyr terrific news, thank you for this fantastic library

[maggie44]

Is there a branch of fork that the work will take place on, to follow progress?

Annoyingly GitHub chooses to abandon useful dates on some posts and chooses to write 'commented last month' on your initial post, so I have no idea if this thread is 15 days old or 45 days old or whether the question is a little premature. Thanks GitHub.

[nhooyr]

@maggie44 Yea sorry it's been exactly a month. I had to stay on a bit longer with Terrastruct than I expected. No other branch to follow progress, will be on dev here.

[maggie44]

Good to know, thanks. I am at the beginning of a new project, been going through my web socket vendor options. The comparison section on the README is very convincing as is the code, and this post is very convincing too.

I came here through a Reddit post that may be worth adding to if you want to highlight that this is being resurrected: https://www.reddit.com/r/golang/comments/zu80o0/gorillawebsocket_or_melody/

[nhooyr]

Haha thanks glad you're considering my library.

I don't have a reddit account anymore unfortunately. I deleted mine after the whole third party app debacle earlier this year. I would appreciate it if you could mention it.

[maggie44]

Haha thanks glad you're considering my library.

I don't have a reddit account anymore unfortunately. I deleted mine after the whole third party app debacle earlier this year. I would appreciate it if you could mention it.

Afraid I don't have one either. Hopefully someone will do the honours.

Thanks for your work on the library. Starting to implement today and will follow along with the progress 👍 (aware of potential breaking changes in v2, will cross that bridge when I get there).