HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
askama-rs
askama-old
Rust2017–2023
askama-rs / askama-old · Archived

askama-old

The original askama repo, please go to https://github.com/askama-rs/askama

Libraries & SDKs
Explore on GitHubRead Hacker News discussions
8Distinct people
10Mentions
0Explicit recommenders
3.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The original askama repo, please go to https://github.com/askama-rs/askama

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 year10 dated mentions

Observed mentions: 2017-03-09 15:27:18 UTC to 2023-11-20 17:32:49 UTC.

01232017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023

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.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC312
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

What Hacker News says

10 sources
neilyio·Nov 20, 2023
This is such a great project, thank you for sharing! It seems like you're getting the usual dump of negativity around HTMX... but as usual, not much coming from anyone who's actually tried to build something small/medium-sized. I keep hearing that this stack "would" fall apart in a bigger project, but I never hear any concrete, empirical descriptions of issues that actually do arise. I'll offer one here... using HTMX usually means you're going to be writing HTML templates, and HTML templating languages don't have much IDE support. I really miss goto-definition etc. when I'm writing Jinja templates. That being said, I've personally found Rust/HTMX to be a magnificent combo. I personally find writing backend endpoints in Rust to be no more cumbersome than any other language (after becoming comfortable with Rust)... and there's massive gains
Read the rest
from the incredible tooling and type system. I wonder if you've considered using Askama for your templates? It has a Axum integration that cleans up some of the boilerplate around template rendering. There's also an open PR for block fragments [1], which will make componentization of HTML fragments much easier, as discussed in this essay on the HTMX site [2]. We need more projects like this to demonstrate how useful, highly-interactive apps are made with HTMX. I'd encourage skeptics to try the same before writing it off. [1] https://github.com/djc/askama/pull/824 [2] https://htmx.org/essays/template-fragments/
In RustGPT: ChatGPT UI Built with Rust, Htmx, SQLite
boredumb·Apr 11, 2023
https://tourofrust.com/ is fun. Learning rust has a weird initial learning curve dealing with the aggressive analyzer/compiler and how you have to approach your variables, but after that initial hump it is one of the coziest languages I've used. Having what was initially a bit of a nag, is now a godsend when i'm getting red-squiggles in vscode for a typo in my SQL string for a misnamed column, or a field in my template was removed and so my struct shows how it's now unused. Rust allows me to mainly only run the application to confirm things work from a business perspective. For people starting out building stuff in rust - understand that there is a distinction of async code and libraries and can lead to confusing compiler errors if you don't realize there is a distinction. It's simple in hindsight but did cause me to waste hours barking u
Read the rest
p the wrong trees at first. Other wise just learn about `match` and Result/Option types asap, they're fundamental. https://github.com/http-rs/tide tide is great to create an http server / routes https://github.com/djc/askama I use this to template out HTML and it checks all my boxes, dynamic data, passing in functions, control flow. https://github.com/launchbadge/sqlx sql interface for a variety of backend, async safe. https://github.com/seanmonstar/reqwest http client to make requests Rust is amazing, don't let the initial few speed bumps discourage you - building real things with rust is no more challenging today than any other modern language stack.
In Becoming Rustacean: Resources to Learn Rust Programming
tazjin·Oct 16, 2022
In strongly typed languages like Rust, composing smaller libraries is usually quite painless, so you don't need a large framework. Personally for backend Rust I use rouille[0] for the server (it's very simple and async-free), askama[1] for compile-time HTML templates and (if a SPA is unavoidable, as that is of course always to be avoided if at all possible) yew[2] for client-side WASM. Now this stack is what I like personally, but there are many options that you can combine, some more full-featured than others. Check out https://www.arewewebyet.org/ for a partial overview. [0]: https://github.com/tomaka/rouille [1]: https://github.com/djc/askama [2]: https://yew.rs/
In Show HN: An Express-inspired web framework for Rust
Winsaucerer·Jun 4, 2022
I don't really know what you mean by serverside HTML generation crate. HTML is just HTML. What I usually need is some templating system, and that can be used to produce HTML, SQL, or whatever else I want. Use askama or tera, for example. Here's an example of using askama with axum: https://github.com/djc/askama/tree/main/askama_axum If you mean something more significant, like what an ORM/query builder is to SQL, then I haven't really had a need for such a thing myself. It's far more likely to get in my way when I stray past common scenarios.
In Async Rust doesn't have to be hard
codetrotter·Apr 6, 2018
I have now rewritten my code so that I include bytes directly in my src/main.rs like so: #[get("/fonts/<fname>")] fn fonts<'a> (fname: String) -> Result<Content<Vec<u8>>, NotFound<String>> { match fname.as_ref() { "autobahn.woff" => Ok(Content(ContentType::WOFF, include_bytes!("../static/fonts/Autobahn/autobahn.woff").to_vec())), "autobahn.ttf" => Ok(Content(ContentType::TTF, include_bytes!("../static/fonts/Autobahn/autobahn.ttf").to_vec())), "grobe-deutschmeister.woff" => Ok(Content(ContentType::WOFF, include_bytes!("../static/fonts/Grobe-Deutschmeister/grobe-deutschmeister.woff").to_vec())), "grobe-deutschmeister.ttf" => Ok(Content(ContentType::TTF, include_bytes!("../static/fonts/Grobe-Deutschme
Read the rest
ister/grobe-deutschmeister.ttf").to_vec())), _ => Err(NotFound(format!("No such file: /fonts/{}", fname))) } } In the meantime since I first wrote my original code, the web framework I was using called Iron [1] has become unmaintained and they now urge people to pick a different framework. I chose to use Rocket because it seemed to have the features I want and the documentation seemed good enough to get started (and it was). For templating I found Askama [2], which I am using from git master in order to be able to use it together with Rocket. https://github.com/djc/askama/issues/71 Eventually I will generate the routes for the included bytes with build.rs again. My new code is better both short-term and for when I will create said build.rs. Thank you masklinn for your comment about include_bytes! which made me look at my code again and rewrite it. [1]: https://rocket.rs/ [2]: https://docs.rs/crate/askama/
In Making a Statically-Linked, Single-File Web App with React and Rust
dochtman·Jul 15, 2017
I actually wrote a JavaScript code generator for Jinja, which allows you to use the Jinja parser and AST and generate pretty readable and fairly sane JavaScript code (for a pretty large subset of full Jinja). I actually used this in my startup (now long dead) where we were able to reuse quite a lot of template code both on the server and the client. https://github.com/djc/jasinja This is in some (conceptual/experiential) ways a precursor to my recent attempt to create a Rusty Jinja-like, which tries hard to take the best ideas from Jinja and mash it up with the best ideas from Rust: https://github.com/djc/askama
In Universal Jinja: a crazy idea for a Python-ready front end

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.