smithy-rs VS minijinja

AWS recently released https://github.com/awslabs/smithy-rs, which is the basis upon which the AWS Rust SDKs are built. The team behind it are still refining it, there’s the odd corner-case with smithy models that will catch it, but it is pretty decent now.

Here's an example of what this looks like in practice: https://github.com/awslabs/smithy-rs/tree/main/rust-runtime/aws-smithy-http-server-python/examples

There’s an older internal schema language for API descriptions, but it can be translated to smithy, so that’s being used for all new sdk’s. See https://github.com/awslabs/smithy-rs for instance.

It's not really a fully finished project yet, so not much. We shipped the AWS SDK for JS v3 with Smithy, the AWS SDK for Go v2 with Smithy, and just launched an alpha of the AWS SDK for Rust using Smithy. More are in the works. We're currently iterating on their code generators to make them easier to use outside the AWS SDKs. AWS SDKs are being built in a layered approach where there's a generic code generator that's really extensible, and then the AWS SDKs extend it to add AWS-specific stuff like regions and credential handling.

We're working to get projects like these to GA: https://github.com/awslabs/smithy-typescript, https://github.com/aws/smithy-go, and https://github.com/awslabs/smithy-rs. And we're also working on service code generation.

MiniJinja v1 - Templating engine

An authentication system is an integral part of modern applications. It's so important that almost all modern applications have some sort of it. Because of their critical nature, such systems should be secure and should follow OWAP®'s recommendations on web security and password hashing as well as storage to prevent attacks such as Preimage and Dictionary attacks (common to SHA algorithms). To demonstrate some of the recommendations, we'll be building a robust session-based authentication system in Rust and a complementary frontend application. For this article series, we'll be using Rust's actix-web and some awesome crates for the backend service. SvelteKit will be used for the frontend. It should be noted however that what we'll be building is largely framework agnostic. As a result, you can decide to opt for axum, rocket, warp or any other rust's web framework for the backend and react, vue or any other javascript framework for the frontend. You can even use rust's yew, seed or some templating engines such as MiniJinja or tera at the frontend. It's entirely up to you. Our focus will be more on the concepts.

I worked on a side project (currently with about 30-50 regular real users) using Rust (with axum), sqlite for the database, minijinja for template rendering, and htmx for the frontend interactivity and S3 for backups. It was quick to hack together (who says Rust is bad for prototyping?), and yet I still feel happy about the code quality. It's been running for a while now in production on fly.io free tier, I noticed it's apparently been using a steady 12MB of RAM, and zero errors or production issues so far since its inception. Last night I decided randomly to benchmark it on my laptop, it can handle 4000+ requests per second hitting the database with a bunch of data inside, I have put almost no effort into optimization. I feel like this might be a good result? Perhaps approaches like this will catch on? Something about this feels pretty cool! Has anyone else had this experience using Rust? I can think of multiple applications (in cluster of microservices) I've come across during my day jobs with large AWS bills and much higher incidental complexity that I would probably choose to do differently given this experience if I had the chance.

Jinja2 vs minijinja-py: not a rewrite per se tho https://github.com/mitsuhiko/minijinja/tree/main/minijinja-py

Thanks to PyO3 and maturin I was able to make pretty decent Python bindings for MiniJinja, which is a Rust reimplementation of most of Jinja2. This in a way is now full circle.

Ronacher has ported jinja2 (partially) to Rust

https://github.com/mitsuhiko/minijinja

If you wan't to know why I even dove down into this Rabbit hole: I wanted to enable borrowing for filter functions in MiniJinja. The PR has more context

Hello, I am developing a CLI program for rendering template files using the new MiniJinja library by /u/mitsuhiko.

github repo