Our great sponsors
-
waggy
The dead simple, easy-to-use library for writing HTTP handlers and routers in Go that can be used in standard HTTP server environments or in WAGI (Web Assembly Gateway Interface) environments
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Initially found out about this via this issue thread here where they were looking for new maintainers.
I have a library that I’ve been working on for a different environment (WASM specifically), but I can be used as a regular HTTP router and provides access to URL path params. Check it out here
I guess speaking to what I perceive as the Node perspective, I kinda don't get the idea that every library, no matter what it does, needs to have commits coming in every week to be "fresh" or it's bad. Me, I see a project with 311 commits that visibly isn't changing every week, and has a very positive community reputation, I see a library I'm more likely to use than the one that is still apparently in constant churn. Why should these codebases be seeing constant churn? What value would they be bringing to me? The standards haven't changed. The web hasn't changed. net/http hasn't changed. Nothing has changed that would necessitate them being in constant churn.
Some other libraries that are actively maintained alternatives to Gorilla websocket: https://github.com/reugn/go-streams https://github.com/kataras/neffos
Some other libraries that are actively maintained alternatives to Gorilla websocket: https://github.com/reugn/go-streams https://github.com/kataras/neffos