Michael Murphy

I think `parallel-rust` / `parallel-rs` are fine.

It's no longer required. The only feature I was using that needed it was mainly just a personal preference, which was finally made stable just recently. I don't use the...

Flume would then be a necessary mpsc channel alternative. They just recently fixed a major bug that made me avoid it for all things async (messages received out of order),...

GLib doesn't have a good way to set up a multi-threaded async runtime. It'd require essentially building your own runtime from scratch. But we could use use [smolscale](https://github.com/geph-official/smolscale) or other...

For now, it's best to stick with GNU Parallel, as this is no longer maintained. One day this will get rewritten with tokio and futures and replaced.

What if we make the API a bit more opinionated to simplify it? Perhaps commands should be dropped by default on shutdown anyway, and if you want something to outlive...

Given that libadwaita comes with strings attached that not everyone wants, pure GTK examples are still useful. It's really just watching the size-allocate signal for your container and then doing...

I'd be willing to pitch in for some examples. For COSMIC we'll be creating a lot of custom widgets, likely as relm4 components. Just having some difficulty with making components...

After a lot of experimentation, `MicroComponents` seems to work as long as every component is implemented manually. That way sub-components can be initialized at the same time and stored alongside...

So far I can't find a single use case for Components that isn't already solved better by MicroComponents. Especially if you want to create a library with reusable components that...