tlssh VS tera

* My own RSS reader (not published. It will never be end-user friendly enough to compete with other ones. But it's better for me)

And then plenty more than I use occasionally, and some I no longer use. E.g. for a while I used my own SSH replacement, in order to get TPM-backed keys (https://github.com/ThomasHabets/tlssh). Nowadays I use yubikey instead (https://blog.habets.se/2016/01/Yubikey-4-for-SSH-with-physic...).

Those are just the main ones (as in not small, and used every day). I find myself fixing problems all the time by writing code.

A curious question. Aside from my day job, this seems like a thing I do all day. :-)

I'm not sure what the motivation for your question is. Do you feel like everything's been invented and built already, and it's just a matter of (at most) plugging the things together?

I find myself constantly thinking "this should exist". I don't have time to make them all exist.

https://github.com/ThomasHabets/arping

Nothing like it existed at the time, and I wanted to send ARP requests as easily as sending ICMP ping.

https://github.com/ThomasHabets/simple-tpm-pk11

I wanted to use a TPM chip for SSH client keys, and couldn't find anything like it.

https://github.com/ThomasHabets/tlssh

I wanted to explore what it would be like to have SSH, but with identities not based on providing username, but an x509 cert. (and TPM chip protecting the key)

You can also use HTML templating with crates like askama, tera and maud! This can be combined with the power of lightweight JavaScript libraries like htmx to speed up time to production. You can read more about this on our other article about using HTMX with Rust which you can find here.. We also collaborated with Stefan Baumgartner on an article for serving HTML with Askama!

Tera, based on Jinja, as the next two

Tera

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.

Or Flask!

My guess is that "fastest" refers to the request-response loop.

I'd be interested in knowing how fast it is once you tack your favourite template rendering engine on top.

It would be nice if it supported Tera, the Rust template engine that is inspired by Jinja2:

https://github.com/Keats/tera

supports sophisticated templating using Tera,

As you might've noticed I have a static www folder with all my files. If I go to /, /login, /register I want to respond with my templated HTML. If the browser asks for another file, such as index.js or something.png I want to serve it from the static folder. I someone wants to access the raw template HTML, such as index.html I want to response with a 404 message.

tera for email templates.

I've been using Tera and Chromium Oxide to generate and render reports to PDF and its been very needs suiting. It can also render to a PNG file.