mitsuhiko

minijinja

Rust2023–2026

mitsuhiko / minijinja

minijinja

MiniJinja is a powerful but minimal dependency template engine for Rust compatible with Jinja/Jinja2

Explore on GitHub Read Hacker News discussions

7Distinct people

7Mentions

0Explicit recommenders

2.8KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

MiniJinja is a powerful but minimal dependency template engine for Rust compatible with Jinja/Jinja2

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year7 dated mentions

Observed mentions: 2023-01-15 00:10:13 UTC to 2026-01-16 21:40:52 UTC.

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	0	1
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	3	2	1
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	1	0	1
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	2	1	1

What Hacker News says

7 sources

gorkaerana·Jan 16, 2026

I think it's fair enough to consider porting a subset of rewriting, in which case there are several successful experiments out there: - JustHTML [1], which in practice [2] is a port of html5ever [3] to Python. - justjshtml, which is a port of JustHTML to JavaScript :D [4]. - MiniJinja [5] was recently ported to Go [6]. All three projects have one thing in common: comprehensive test suites which were used to guardrail and guide AI. References: 1. https://github.com/EmilStenstrom/justhtml 2. https://friendlybit.com/python/writing-justhtml-with-coding-... 3. https://github.com/servo/html5ever 4. https://simonwillison.net/2025/Dec/15/porting-justhtml/ 5. https://github.com/mitsuhiko/minijinja 6. https://lucumr.pocoo.org/2026/1/14/minijinja-go-port/

In Cursor's latest “browser experiment” implied success without evidence

tosh·Jan 13, 2026Submission

MiniJinja is a powerful but minimal dependency template engine for Rust

2 points · Open discussion

petcat·Sep 3, 2025

> As part of my ongoing project to reimplement Django’s templating language in Rust, I have been adding support for custom template tags. Cool project, but does the author know about minijinja [1]? [1] https://github.com/mitsuhiko/minijinja

In Sharing a mutable reference between Rust and Python

GamePad64·Nov 24, 2024Submission

Show HN: Notifico – Open-Source notification server with Email & Slack support

Hello, HN! I have built an open source notification server, that supports Email, SMS (SMPP), Slack, Telegram, WhatsApp Business. It is called Notifico. I have worked in a bunch of tech companies, and in each of them there was a half-baked, in-house built notification server for sending emails and other notifications. So, I've collected the requirements, processed them and written the implementation in Rust! The idea is simple: You send event_id and context (JSON object), and It loads the template, renders it with variables from the context, sends it to the recipient. Features: - No-code configuration. No knowledge of JS or other language is required. - The templates can be edited without the need of backend developers. - HA configuration with AMQP 1.0 support (e.g., RabbitMQ). Every component scales horizontally. - Powerful templating la

Read the rest

nguage (it uses minijinja internally: https://github.com/mitsuhiko/minijinja) - List-Unsubscribe support - Admin interface for managing Events, Templates, and Pipelines. Roadmap: - Discord support - Mattermost support - Bounce email handling - User-facing API for managing subscriptions - Message view tracking and statistics. - Tracking pixels - Notification center implementation for Web and Mobile. - Auto-retry for failed messages - Template and Pipeline versioning

4 points · Open discussion

skeptrune·Nov 21, 2024Submission

Show HN: PDF2MD – Rust+Redis+ClickHouse+VLLM conversion pipeline for PDFs

If you just want to use it, try here - https://pdf2md.trieve.ai . I think the LLM's are astoundingly good at converting complex powerpoint style infographics. I wouldn't normally think folks on HN would find this interesting as the general concept has been posted about already in the past few months. We were heavily inspired by Zerox[1]. However, the stack we went with was fun and over-engineered which is more likely to create interesting discussion. We use all the same tools at Trieve (our main product), but wanted to see if they would be a good fit for something that needed to get built in a tighter timeline and we think they were! Took us 2 weeks to get this setup end-to-end and it's by no means complete (see roadmap in linked README). However, it's cool that a relatively cookie cutter web service like this can be created with pure ope

Read the rest

n-source dependencies and non-standard Rust tooling so quickly. Rust won't kill your startup! - Minijinja templates for the UI[2] - PDFObject for doc display in-browser[3] - actix/actix-web HTTP server framework[4] - Redis queue macro for worker async processing[5] - Clickhouse for task storage[6] - chm CLI to handle Clickhouse migrations[7] - MinIO S3 for object storage[8] [1]: https://news.ycombinator.com/item?id=41048194 [2]: https://github.com/mitsuhiko/minijinja [3]: https://github.com/pipwerks/pdfobject [4]: https://github.com/actix/actix-web [5]: https://github.com/devflowinc/trieve/blob/main/pdf2md/server... [6]: https://github.com/ClickHouse/ClickHouse [7]: https://docs.rs/chm/latest/chm/index.html [8]: https://github.com/minio/minio

13 points · Open discussion

throwaway313373·Oct 22, 2024

Re ORM: fair enough, I don't have any experience with Diesel, just wanted to know if you have an actual reason or if it's just a case of NIH [0] syndrome :) Re templates: I understand that writing a new template engine can be a very fun task (it is both hard enough not to be boring and easy enough not to feel daunting). I also thought many times of creating my own template engine to fix things that I don't like in the language that I am currently using (mostly jinja2). But if you intend this project to become an actual production ready solution, I see a lot of good reasons not to reinvent template language: 1. Forcing users to learn yet another template language is an additional entrance barrier 2. Tooling support. Existing languages might already have a good tooling support (coming from Python world: PyCharm supports both Django template

Read the rest

s and jinja2 very well) including syntax highlighting, auto-complete, auto-formatting, linting etc. Are you going to create all of it yourself? 3. You mentioned planned migration from Python. How exactly I am supposed to manage templates during the transition period? Do I have to have two copies of each template: one in legacy language and one in your new language? If you had a template language compatible with Django/jinja2 [1] this problem would not arise. 4. Whether we like it or not more and more people are using LLMs for coding. This potentially could solve the issue of migrating templates. I expect LLMs to perform really well on the task of "translating" a template from a <popular template language A> to a <popular template language B>. The problem is that if your template language is brand new, LLMs probably didn't have enough examples in their training sets to "learn" its syntax. So, basically, you are setting up your users for a boring, tedious and error prone task of rewriting each template manually without a proper support from their IDE/editor. Meh. BTW, Django makes it very easy to bring your own template engine [2]. [0] https://en.wikipedia.org/wiki/Not_invented_here [1] https://github.com/mitsuhiko/minijinja [2] https://docs.djangoproject.com/en/5.1/howto/custom-template-...

In Show HN: Rust Web Framework

VWWHFSfQ·Jan 15, 2023

Ronacher has ported jinja2 (partially) to Rust https://github.com/mitsuhiko/minijinja

In Show HN: Robyn – A fast, extensible async Python web server with a Rust runtime