Mastodawn

Diniremix May 2

Awesome #axum
#rustlang 🦀

https://github.com/szabgab/awesome-axum

GitHub - szabgab/awesome-axum: Tutorials, showcases and extensions for the axum web site building crate written in Rust

Tutorials, showcases and extensions for the axum web site building crate written in Rust - szabgab/awesome-axum

GitHub

musicmatze

Apr 12

So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

Dmitry Marakasov Apr 10

It looks like #axum is finally going to get proper route matching with prefixes and suffixes support (e.g. `/images/{foo}.jpg`, while before only `/images/{foo}` was supported).
https://github.com/tokio-rs/axum/pull/3702

Bump matchit to 0.9.2 by AMDmi3 · Pull Request #3702 · tokio-rs/axum

Motivation Explained in #3140 - primarily to be able to use very desired prefixed or suffixed captures in routes, such as router.route("/{id}.png"). Solution The work had already been don...

GitHub

Slatian Apr 10

Can some rustlang fluent creature help me with an axum problem?

I want to write some middleware that reads a cookie, a header does some value choosing that it needs some configuration for and attached the result to the request.

Currently this is implemented using an axum middleware function with state that is passed through axum::middleware::from_fn_with_state to turn it into a layer, but I want to turn it into a Layer struct, but I keep running into type problems.

async fn middleware(
	State(arc_state): State<Arc<LanguageManifest>>,
	cookie_header: Option<TypedHeader<headers::Cookie>>,
	mut req: Request<Body>,
	next: Next,
) -> Response {
 […]
}

#rustlang #axum

Diniremix Apr 8

#Salvo vs. #Axum: A Tale of Two Design Philosophies

#rustlang

Qiita - 人気の記事 Mar 16

Rust バックエンドで htmx を使ってみた
https://qiita.com/nakamura-yzrh/items/8793a51e71ef76b0f5d8?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Rust #tokio_rs #askama #axum #HTMX

Rust バックエンドで htmx を使ってみた - Qiita

htmx とは htmx は「HTML中心で動くフロントエンド」を実現するための軽量な JavaScript ライブラリです。 React / Vue などのフロントエンドフレームワークとは異なり、バックエンドからは JSON ではなく HTML を受け取り、DO...

Qiita

musicmatze

Mar 13

What #axum tutorials do I want to check out for a full app using #tailwind with #daisyui and maybe even #datastar

#rust #rustlang

Show thread

Michał Fita Mar 7

@pointlessone @rayk @tomekw I'm afraid you have biased view. There are two angles to the "web frameworks".

1. #Axum and #Rails don't even play the same sport, the former's performace comes at cost of orders of magnitude more complex implementation; it was never intended to be #Django in #Rust

2. The fact we have web frameworks in Rust is "an accident", the language was never intended to specifically write ones. Rust is a proper system programming language, the same class as C (not #Go w/GC).