waggy
neffos
| waggy | neffos | |
|---|---|---|
| 8 | 1 | |
| 38 | 563 | |
| - | - | |
| 3.0 | 6.1 | |
| about 1 year ago | 27 days ago | |
| Go | Go | |
| BSD 3-clause "New" or "Revised" License | MIT 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.
waggy
-
what's your recommended router? chi, mux, something else?
Chi for work, my own router for personal projects
-
Waggy hits v0.8.0 with support for custom middleware, listening and serving on a specific host and port address, and more!!
And in that time, I’ve gotten the router I’ve been working on, Waggy, up to a new version of v0.8.0!! Along with some minor bug fixes, some refactoring, and restructuring changes, there is now full support for custom middleware and listening and serving on a specific host:port address.
-
What mux/router to use now a days?
For work, we’ve switched to Chi. For personal projects, I use a router I’ve been built and have been working on myself
-
Gorilla Web Toolkit is now in archive only mode
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
-
Waggy v0.3 Released!!
Waggy v0.3 is out now!! Along with some minor bug fixes, v0.3 comes with two major improvements, being the ability to configure loggers for WaggyRouters and WaggyHandlers alike, as well as a convenience wrapper for serving files as responses. One other big unplanned, but welcome improvement is the ability to use Waggy in conjunction with Fermyon’s Spin Go SDK for writing WAGI microservices that can also make outgoing HTTP calls.
-
Waggy v2 Release
Waggy has released v2!!
-
The best Go framework: no framework? (Three Dots Tech)
With the rising popularity of WASM, I’d probably use something like wazero coupled with the library I just wrote and released, waggy for writing the individual handlers for each route, though.
- Waggy: A dead simple library for writing WAGI API Handlers in Go
neffos
-
Gorilla Web Toolkit is now in archive only mode
Some other libraries that are actively maintained alternatives to Gorilla websocket: https://github.com/reugn/go-streams https://github.com/kataras/neffos
What are some alternatives?
gorilla-mux - A fork of gorilla/mux, the powerful HTTP router and URL matcher for building Go web servers with 🦍
ws - Tiny WebSocket library for Go.
httprouter - A high performance HTTP request router that scales well
go-streams - A lightweight stream processing library for Go
jwtauth - JWT authentication middleware for Go HTTP services
otelchi - OpenTelemetry instrumentation for go-chi/chi
spin - Spin is the open source developer tool for building and running serverless applications powered by WebAssembly.
mux - A powerful HTTP router and URL matcher for building Go web servers with 🦍
restruct - RESTruct is a rest router written in Go to automatically create routes based on your structs.
useful-forks.github.io - Improving GitHub's Forks list discoverability through automatic filtering. The project offers an online tool and a Chrome extension.
wazero - wazero: the zero dependency WebAssembly runtime for Go developers