useful-forks.github.io VS waggy

Here "branches" is for Git branches - or, rather, forks - of the emulator project. It means checking GitHub (or https://useful-forks.github.io/) to see if any individual developers have recently forked the project and made new commits. If so, you can try to build the updated project, and see how it goes.

Find alternatives or use useful fork

gorilla/mux is at least more battle-tested. I'd rather fork it myself, or evaluate a useful fork of it such as this one (if it seems well-maintained, I haven't done the leg-work).

An acquaintance of mine built this: https://github.com/useful-forks/useful-forks.github.io

Chi for work, my own router for personal projects

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.

For work, we’ve switched to Chi. For personal projects, I use a router I’ve been built and have been working on myself

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 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 has released v2!!

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.