Our great sponsors
-
v
Simple, fast, safe, compiled language for developing maintainable software. Compiles itself in <1s with zero library dependencies. Supports automatic C => V translation. https://vlang.io
-
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.
I've been working on https://github.com/hapsoc/hring for a while and I'm almost at the point where I should put it in production somewhere — I'm curious how it performs.
Have you tried V (Vlang)? https://github.com/vlang/v
any advice for library writers re: making sensible APIs? I've been working on a .NET-adjacent Rust library for a couple years now but have kept it unreleased to iterate on design for a while (although the repo is here if you're curious), but I'm getting close to release and need to start making decisions about overall structure. in your opinion, what kind of API considerations make a complicated framework easier to grasp?