You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected to see some wording about how the package is retired (which it is according to #2134) and should not be used
What did you see instead?
I saw completely normal looking documentation for a package with no warning or indication that the package is retired. There is the suggestion that the package "lacks some features" found in other libraries, but as my needs are very basic, that did not stand out to me as a problem.
Luckily, I tried reasoning about the API and couldn't understand how one would read frames whose length is a multiple of len(buf) and asked someone on IRC who pointed out that the aforementioned issue claims the package is retired.
Since the library is retired, and the API is problematic (for reasons discussed in the other issue), I believe the docs page should make it clear that new code should not be written using x/net/websocket. As it is part of the high-profile and official x/net, I'm probably not the first or last person to gravitate towards it.
The text was updated successfully, but these errors were encountered:
What is the URL of the page with the issue?
https://pkg.go.dev/golang.org/x/net/websocket
What is your user agent?
N/A
Screenshot
What did you do?
I read the documentation
What did you expect to see?
I expected to see some wording about how the package is retired (which it is according to #2134) and should not be used
What did you see instead?
I saw completely normal looking documentation for a package with no warning or indication that the package is retired. There is the suggestion that the package "lacks some features" found in other libraries, but as my needs are very basic, that did not stand out to me as a problem.
Luckily, I tried reasoning about the API and couldn't understand how one would read frames whose length is a multiple of
len(buf)
and asked someone on IRC who pointed out that the aforementioned issue claims the package is retired.Since the library is retired, and the API is problematic (for reasons discussed in the other issue), I believe the docs page should make it clear that new code should not be written using x/net/websocket. As it is part of the high-profile and official x/net, I'm probably not the first or last person to gravitate towards it.
The text was updated successfully, but these errors were encountered: