wasmws
websocket
wasmws | websocket | |
---|---|---|
5 | 15 | |
61 | 3,482 | |
- | - | |
0.0 | 8.7 | |
over 2 years ago | 23 days ago | |
Go | Go | |
Mozilla Public License 2.0 | ISC License |
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.
wasmws
-
Is there an alternative to gorilla websocket?
Thanks for writing this! I found it really great to use when I wrote https://github.com/tarndt/wasmws
-
Goomerang 🪃 A protocol buffers over websockets communications library
Before looking at the readme, I thought this was an alternative to using https://github.com/tarndt/wasmws which lets you use gRPC over websockets so that you can use gPRC via WASM without needing an http to gRPC gateway. Now I'm understanding a bit differently. It looks like this uses protobufs but doesn't have anything to do with gRPC at all, instead implementing some of the communication parts of gRPC while ignoring the generation of services but instead focusing a bit more on message routing and pub/sub that you would probably still need NATS.io for if you were using gRPC.
-
Even More Minor Features in Go 1.18
The hijacking a websocket works very well, live in the future today! https://github.com/tarndt/wasmws
-
Migrating from nodejs to go codebase using gopherjs
Everything said above is valid, but if you do think you have a need to transpile... consider running any Go frontend code as WASM rather than Javascript. A few years ago I started doing my frontends and backends all in Go and its been wonderful. I even wrote a library so I could use gRPC from my WASM/Go frontends rather than REST: https://github.com/tarndt/wasmws . Extra wonderful, at least for my tastes. Once caveat is if your brotli compressed, CDN/browser cached, etagged Go WASM is still to big, you can usually make it even smaller by using tinygo rather than the std tool chain for the compiling to WASM.
-
Go and gRPC is just so intuitive. Here's a detailed full-stack flow with gRPC-Web, Go and React. Also, there is a medium story focused on explaining how such a setup might boost efficiency and the step-by-step implementation.
A while back I was writing a pure Go frontend app (WASM) and I wrote this so I could use gRPC rather than REST to talk to my backend: https://github.com/tarndt/wasmws
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
- Gorilla Web Toolkit is now in archive only mode
-
Gorilla toolkit maintainers are stepping down and have been looking for new maintainers. The project could otherwise be archived.
There's https://github.com/gobwas/ws and https://github.com/nhooyr/websocket but neither have seen a commit in over a year
-
Goomerang 🪃 A protocol buffers over websockets communications library
The last time I was using websockets, I found https://github.com/gobwas/ws to be a huge improvement over Gorilla, but I haven't been looking recently, and perhaps Gorilla was able to shed some of its bloat and improve API and performance since then.
What are some alternatives?
goomerang - A small communications library based on protocol buffers over websockets
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.
wombat - Cross platform gRPC client
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
grpc-web - gRPC for Web Clients
NATS - Golang client for NATS, the cloud native messaging system.
goja - ECMAScript/JavaScript engine in pure Go
ws - Tiny WebSocket library for Go.
Ebiten - Ebitengine - A dead simple 2D game engine for Go
ote - ote updates a packages' go.mod file with a comment next to all dependencies that are test dependencies; identifying them as such.
go-quilljs-delta