Otto Chrons

I would prefer focusing on good documentation and examples, without doing any code level support for databases in Dioxus. The database is a very orthogonal concern to UI building, so...

I have a related issue of building a router with language prefixes such as ``` /en/blog/post/1 /es/blog/post/1 /de/blog/post/1 ``` One workaround would be to wrap it with `#[nest("/lang/:lang")]` but that...

I worked around this problem with following route definition using the undocumented `#[child]` attribute and using a layout wrapper to store the language into context ```rust pub enum BaseRoute {...

With some further tweaking I was able to optimize it down to this, which works well for me. ```rust #[derive(Clone, Debug, PartialEq, Routable)] pub enum BaseRoute { #[nest("/:lang")] #[layout(LanguageWrapper)] #[child("")]...

I'm getting this same issue when trying to access Fake S3 from inside a Docker container with `fakes3` running on the host. Using 172.17.0.1 as host address, resulting in a...

Yeah, Node version is not concurrent at all. If we allow for that, all examples would be quite different and probably perform better since the actual "computation" is a no-op.

Or just run it for 10M or 100M iterations :) Go runs out of memory soon after 10M iterationrs, while the Scala Future version is totally stable with practically no...

Using Akka actors for something like this is pointless and a bad example for actor usage. Would be different if the benchmark first initialized an actor hierarchy and then did...

It's now in a separate `scala-future` dir with a bit of warm-up added.

@ogier going from `Future.successful(x)` to `Future(x)` does impact performance, from 230ms to 380ms. Then again, this is how it would be idiomatically implemented with Scala futures, so why would you...