meta: Status update and v2.0.0 holy grail requests

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

Không có tệp, bài kiểm thử hay entry point nào được nêu. Hãy bắt đầu bằng việc xem xét các issue còn tồn đọng và các tính năng được yêu cầu được tham chiếu ở đây, sau đó xác định một thay đổi cụ thể cho v1 hoặc một đề xuất API v2 đã được hoàn thiện; để được coi là hoàn tất, cần có phạm vi được xác định và một kế hoạch được phản hồi hỗ trợ, thay vì roadmap chung chung trong issue này.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.