CubeSimRS VS axum

Been putting further work into my Rubik's Cube solver. Managed to get a basic solver working using some variation of IDA*. Planning to refactor the code and then start optimising to make things go fast.

Been working quite extensively on my Rubik's Cube simulator and solver. Currently working on optimising my data structures and then eventually to getting a proper solver working.

Completely new and picked up Rust about 10 days ago. Started by heading straight into a project of making a Rubik's Cube solver while following the Rust book along the side.

You have a couple of options for the underlying web framework to pair with Leptos: Axum or Actix. Axum seems to carry more favour currently, so we start with that. Assuming you already have Rust set up on your system:

I’m the author of https://kellnr.io. When I started working on Kellnr three years ago, https://rocket.rs was “the web framework” to use. Unfortunately, the project seems dead. Before adding more functionality using an unmaintained framework, I want to port Kellnr to https://github.com/tokio-rs/axum.

Web Framework : axum.

I am trying to stream a response from the OpenAI API as an SSE with axum. I have combined the following examples from the async-openai and axum repos to produce the below code I've used iterators in Rust but have not used streams, I have no idea how to reconcile the types here and don't know where to start to solve the problem. A solution or any pointers would be greatly appreciated. https://github.com/tokio-rs/axum/tree/axum-v0.6.20/examples/sse https://github.com/64bit/async-openai/tree/main/examples/chat-stream ``rust async fn sse_handler( TypedHeader(user_agent): TypedHeader, ) -> Sse>> { println!("{}` connected", user_agent.as_str());

-- axum README

Perseus applications also make use of tokio, a Rust asynchronous runtime, and perseus-axum — an integration that streamlines the use of the Perseus frontend framework with the Axum web framework, specifically on the engine side. The configuration file also shows a section for browser-only dependencies. Even though there are no default dependencies in this section, it indicates a place where such dependencies could be added as your application evolves.

Take a look at some well designed project structure https://github.com/tokio-rs/axum

Axum https://github.com/tokio-rs/axum has great examples for quick start.

Tokio is a runtime for asynchronous programming for Rust; Axum is a web framework that leverages the former. I already used Axum for the previous REST API, so I decided to continue.

The environment is not as mature as in dotnet, but there are some hidden gems like Axum: check it out if you have time :)