Already testing the new release on some small services I'm running at home, other than the breaking changes to path parameters it's been a painless upgrade. I'm going to upgrade the Axum services at work in the coming weeks.

I've only written projects in Rust either from the beginning or rewritten in parallel with an existing version, so it's quite inspiring to see a project successfully doing an in-place rewrite. Gaining insight into this process definitely helps with some things I'm working on.
🧵 2/2

Combined with a proper CI/CD stack which notifies the ones involved about errors and prevents deploying broken builds and you're golden. 95% of the time it's not about pinning blame, but rather helping everyone improve.
As a bonus it helps onboard juniors and establish good practices from day 1.
2/2

Unfortunately some people have to be forced to use a strict compiler or linter to prevent them from doing stupid, fast and easy fixes. Even if they know better. Having tools which slap you and say "NO! That's stupid, do this instead" is very useful in a corporate context.
1/2

I fully agree with you. In this case we have to be 200% sure the data is correct and valid, while dealing with unsanitized user input. Most of my frustration is with the sanitization "layer", it should be implemented in something strict. Afterwards the data can and should flow freely.

There's always the possibility we could cook up our own monad data structures or converting things to #Typescript so we could use fp-ts or effect-ts. The only problem is the huge codebase. We are already considering converting it to #Rust, #Elixir with typespecs, or #Gleam.

#programming #rustlang