Offline
Now one might themselves silly questions like 'why'? Why would you have touch velocity for window placement? Why not accept the placement when the position 'overshoots' the target zone?
I can answer none of these questions, but I kinda like it. More window management operations should be skill-based.
Did you know that Catacomb's window manager has built-in curling?
Just tile a window, switch to the overview, then try and land it in the target zone using touch velocity!
Catacomb's 1.4.0 release is out, with some minor QoL improvements:
- Double-tap on the gesture handle now turns the display off
- Better iio-sensor-proxy support
- Improved touch velocity with different output scales and input polling rates
@YaLTeR @postmarketOS Well the audio would have to work reliably in the first place. 
While working on #servo recently, I came to the realization how much Rust isolates itself from other languages, just by not providing a C interface by default.
We can't write a browser engine for every programming language. While using Servo is a breeze in Rust, using it with any other language seems problematic.
The Linux Kernel managed to adopt Rust, I wrote a Rust WebKit browser, but I'm not sure what the future holds for Servo when it's time for Rust to say goodbye.
A little preview of the multi-engine behavior in Kumo:
To quickly try out a website in a different engine, you can just reload it in WebKit/Servo through the context menu.
Kumo will remember which engine was last used for a domain and use that engine for all new tabs for that domain going forward. That way if you're interested in a new browser engine, you can transition one website at a time, rather than requiring a complete browser change.