minijinja VS rust

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

If you haven't dipped your touch-typing fingers into Rust yet, you really owe it to yourself. Rust is a modern programming language with features that make it suitable not only for systems programming -- its original purpose, but just about any other environment, too; there are frameworks that let your build web services, web applications including user interfaces, software for embedded devices, machine learning solutions, and of course, command-line tools. Since a custom GitHub Action is essentially a command-line tool that interacts with the system through files and environment variables, Rust is perfectly suited for that as well.

Here's an example of someone citing a disagreement between CRT and shell32:

https://github.com/rust-lang/rust/issues/44650

This in addition to the Rust CVE mentioned elsewhere in the thread which was rooted in this issue:

https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html

Here are some quick programs to test contrasting approaches. I don't have examples of inputs where they parse differently on hand right now, but I know they exist. This was also a problem that was frequently discussed internally when I worked at MSFT.

    #include 

> instead of choosing a certain numbered version of the random library (if I remember correctly) I let cargo download the latest version which had a completely different API.

Yeah, they didn't follow the instructions and got burned. I still think that multiple things went wrong simultaneously for that experience. I wonder if more prevalent uses of `#[doc(alias = "name")]` being leveraged by https://github.com/rust-lang/rust/pull/120730 (which now that I check only accounts for methods and not functions, I should get on that!) so that when changing APIs around people at least get a slightly better experience.

Almost fixed the compiler: https://github.com/rust-lang/rust/pull/123325

Rust: A secure, efficient, and modern programming language (omitting ten thousand words). You can simply follow the installation instructions provided on the official website.

Recently did something similar in Rust but for generating SVGs. We've adopted it for snapshot testing of cargo and rustc's output. Don't have a good PR handy for showing Github's rendering of changes in the SVG (text, side-by-side, swiping) but https://github.com/rust-lang/rust/pull/121877/files has newly added SVGs.

To see what is supported, see the screenshot in the docs: https://docs.rs/anstyle-svg/latest/anstyle_svg/

We strongly believe in Rust as a powerful language for building production-grade software, especially for systems like ours that run alongside Kubernetes.

The above Assert<{N % 2 == 1}> requires #![feature(generic_const_exprs)] and the nightly toolchain. See https://github.com/rust-lang/rust/issues/76560 for more info.