This looks really cool!

Have always wanted to dip my toe in EventStoreDB/Kurrent but this looks super intuitive and nice to use. Especially like the js projections, can imagine it being really handy in prototyping or ad-hoc reporting.

Nice thing about Monads in JS with tools like neverthrow is that you can create the Monad boundary where you like.

It becomes very similar to try-catch exception handling at the place you draw the boundary, then within the boundary it’s monad land.

If you haven’t wrapped it in a monad, chances are you wouldn’t have wrapped it in a try-catch either!

About a week ago I was thinking about how much something like this is needed in Rust. Especially something web-framework and DB agnostic.

Great work, I’m sure this will save numerous dev-hours

But late but I saw this comment and it really spoke to me. I couldn’t agree more.

I have the afternoons of my past week trialling to see if you could achieve something similar to Toasty with just structs and proc macros.

https://github.com/jayy-lmao/sql-db-set-macros

Still WIP but made it past the hurdle of inserts, which I decided to generate a type-state builder pattern to enforce non-nullable fields and skip auto-fields. This is more intended as a proof of concept but I’ll see how much I can grow it and whether I can dogfood at my job

After looking at tRPC, and having done a lot in a few jobs with GraphQL codegen & gRPC codegen, I always wondered why there were so few recent OpenAPI based codegen/client-server-contract tools. I think I was searching for this exact tool.

Love that it makes the client somewhat backend agnostic, but the tools for the OpenAPI backend also look great.

Thank you for this, I hope it is successful in achieving some adoption!

Thanks for the encouraging words! So far it’s already nice to see these libraries being adopted slowly by more and more companies. Not nearly as big as graphql and trpc of course.

Without a doubt DBeaver!

PgAdmin never got me out of the psql terminal but DBeaver has been a pleasure to use

I sure hope this is the unit of measurement and not a Berserk reference

I’ve got to disagree a little. Revealing my bias: I’m a former TS full stack who now works full time in a company that uses Rust on the backend (not my choice). I’ve done so for over a year now.

I find it’s a bit like C# in some ways, especially it’s ability to scale the codebase. Code navigation is incredibly clear and the libraries have been great. The experience of using async-graphql and sqlx is unbelievably intuitive.

For the bad: the compilation times can still be a little slow (especially in CI). This sometimes makes dev a just slightly awkward. I’ve had to contribute to a couple of libraries we depend on because they are still quite young, and we’ve had to move web framework once. Hiring might also be a slight challenge.

I’m not sure if I’d necessarily pick it again if I was to choose for a small business again - but frankly using it has still been a pleasure and the ecosystem is only feeling better.

use rust distributed cached builds, couple liners on ci. vendor stuff. for example nix crane can be good.

Shout out to Unruly Software! Love these guys.

Australian dev duo. Casual conversations around web dev, mostly the experiences of the hosts over the last month or so. Informative but relaxed.

10/10 parasocial relationship

Personally I’ve done a small amount of reading of the Hands On Functional Programming in Rust book. I’ve also found Scott Wlaschin’s F# resources quite transferable (though you may run into some issues with passing async functions around as arguments).