not-yet-awesome-embedded-rust VS tera

And a list of things missing: https://github.com/rust-embedded/not-yet-awesome-embedded-ru...

Building a portfolio is a great idea. Also you can find various areas to contribute to Rust. That would give you great exposure. Check out the not yet awesome rust repo (https://github.com/rust-embedded/not-yet-awesome-embedded-rust) for ideas. Also take a look at the rust foundation grant program, it’s open for applications now. There’s also the “this week in Rust” newsletter (https://this-week-in-rust.org) where job openings relative to Rust are also listed. Lastly, you can check my bio for a link where I provide a list of project ideas for different areas in embedded including Rust.

See Not Yet Awesome Embedded Rust for some ongoing work to build out the ecosystem, it's not ready yet. (this is a play on various "Awesome XYZ Rust" lists that have resources for different topics)

Not Yet Awesome Embedded Rust

Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.

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.