fiber

From nbio's README: For regular connection scenarios, nbio's performance is inferior to the standard library due to goroutine affinity, lower buffer reuse rate for individual connections, and variable escape issues. From gnet's README: gnet and net don't share the same philosophy in network programming. Thus, building network applications with gnet can be significantly different from building them with net, and the philosophies can't be reconciled. [...] gnet is not designed to displace the Go net, but to create an alternative in the Go ecosystem for building performance-critical network services. Frankly, I think it's unfair to argue that the net package isn't performant, especially given its goals and API surface. However, the net/http package is a different story. It indeed isn't very performant, though one should be careful

Go strings are supposed to be immutable. I see that fiber goes behind your back and produces potentially mutable strings behind your back: https://github.com/gofiber/utils/blob/c338034/convert.go#L18 And… I actually don't have an issue with it to be honest. I've done the same myself. But this mutability should never escape. I'd never persist in using a library that would let it escape. But apparently… it's intentional: https://github.com/gofiber/fiber/issues/185 Oh well. You get what you ask for. Please don't complain about maps if you're using a broken library.

That was probably done by fiber[1] the code specifically took the param from it in the function passed to the Get(path string, handlers ...Handler) Router function. c is the *fiber.Ctx passed by fiber to the handler. My code took the string from c.Param("name") passed it to url.QueryUnescape then another function which had a mutex around setting the key/value in the map. I got the hint it was slices and something modifying the keys when I found truncated keys in the key list. My guess is fiber used the same string for the param to avoid allocations. The fix for it is just to create a copy of the string with strings.Clone() to ensure it does not get mutated when it is used as a key. I understand it was an issue with my code, it just wasn't something I expected to be the case so it took several hours and using the debugger to find the root

HTMX is incredible, I adore it. Typically, my stack for a web app is a Golang webserver using Fiber[0], HTMX, SCSS, my own (experimental) templating engine [1] and SQLite. It's a sufficiently hype-free stack, in my opinion, and one that's been fairly well battle tested (bar the templates) and is pretty simple. It's a joy to use! [0]: https://github.com/gofiber/fiber [1]: https://github.com/codemicro/go-neon

I use Fiber [0] in production for a $4M ARR company and never had any issues even at peak traffic. Took less than a month to start with and integrate and it is a joy to use. [0] https://github.com/gofiber/fiber

I use Fiber (https://github.com/gofiber/fiber) for APIs and SolidJS (https://www.solidjs.com) for web UIs.

> nothing really stopping you, but it's not the usual approach In my experience, if you open-source a project, it better have to follow conventions. Following conventions makes sure someone else can read your code easily. > In which directory to store files is an incredibly small and minor detail though. Yeah it's a small detail, but it is important to me to not get lost in a directory tree. Random example taken from a github search: https://github.com/gofiber/fiber Is it really ok to have that much source code at the toplevel? Is the code architecture clear at a glance? For me, it is not, and I'll have to put in extra work (I'm lazy) to understand the code and how it works. I don't mind doing that for other projects, but for my projects as I work on them daily, it becomes a pain very quickly.

With the performance coming from being based on fasthttp, what does the framework offer on top? The README doesn't really mention any features explicitly (other than soft ones like "secure" and "fast"). A comparison with other fasthttp-based frameworks like https://github.com/savsgio/atreugo or https://github.com/gofiber/fiber would also be interesting. Or maybe a benchmark along the lines of https://github.com/smallnest/go-web-framework-benchmark. Looking at the commit history (7 commits, most of them from yesterday), the open issues (no way to define URL path variables yet, https://github.com/abahmed/gearbox/issues/15), and the release being v0.0.1, maybe it's a bit too early for a ShowHN? But if you have a vision of how it will be different and better than existing frameworks and the willingness to keep working on your project, then ho

Benchmarks: (Graph) https://github.com/gofiber/fiber#benchmark (Tech empower) https://fiber.wiki/benchmarks