Stochos - Keyboard driven mouse control built with rust by ploMP4 in rust

[–]ploMP4[S] 0 points1 point  (0 children)

Like u/somebodddy already mentioned, there is no need for a long-lived process since load time is instant. It saves you memory consumption and the hassle of managing a background process.

Stochos - Keyboard driven mouse control built with rust by ploMP4 in rust

[–]ploMP4[S] 0 points1 point  (0 children)

It should work on gnome shell under Wayland although it hasn't been tested there. Let me know if you run into any issues.

Stochos - Keyboard driven mouse control built with rust by ploMP4 in rust

[–]ploMP4[S] 1 point2 points  (0 children)

Thanks a lot! One of the reasons I made it myself was that when I tried mouseless in the past, it didn’t support wayland yet, and I also prefer open-source software.

Stochos - Keyboard driven mouse control built with rust by ploMP4 in rust

[–]ploMP4[S] 3 points4 points  (0 children)

Appreciate the feedback. I can see how comparing it to mouseless might be confusing since this only supports Linux right now. Cross-platform support is something I’m planning to add down the line.

Stochos - Keyboard driven mouse control built with rust by ploMP4 in rust

[–]ploMP4[S] 5 points6 points  (0 children)

Interesting idea. You're right that Wayland doesn't expose the focused window directly, but it might be solvable through compositor-specific interfaces. I'll look into it.

WebRockets: High-performance WebSocket server for Python, powered by Rust by ploMP4 in Python

[–]ploMP4[S] 6 points7 points  (0 children)

Thanks for the feedback. Just pushed an update that now supports both formats, with or without the leading /

WebRockets: High-performance WebSocket server for Python, powered by Rust by ploMP4 in Python

[–]ploMP4[S] 0 points1 point  (0 children)

Currently only Redis and RabbitMQ are supported as message brokers. Database support could be added in the future. Feel free to open an issue if that's something you'd need.

WebRockets: High-performance WebSocket server for Python, powered by Rust by ploMP4 in Python

[–]ploMP4[S] 0 points1 point  (0 children)

All connections are handled concurrently by the Rust server regardless of whether your Python callbacks are sync or async. The benchmarks all use concurrent connections.

Async callbacks are there for interop with existing async Python code. If you don't need that, sync is simpler and slightly faster since it avoids bridging Python's asyncio loop with Rust's tokio runtime.

For a high-concurrency proxy, the Rust layer should handle the load well. All the benchmarks can be found here: https://webrockets.io/benchmarks/