I’m pleased to announce that our much awaited (pun intended) 2.0 stable release is out! While 1.x release was well received, the lack of asynchronous API was the most requested feature. 2.0 API not only provides that but in fact the async API is now the primary one and blocking API is a convenience wrapper around it.
For those who’re not familiar with zbus, it’s a pure Rust library that aim to make D-Bus handling as easy as possible. D-Bus is a inter-process communication (IPC) mechanism that’s very popular on Linux (especially desktop and embedded systems). Many services (e.g systemd, NetworkManager, Geoclue etc) uses it so if you ever find yourself interfacing with them in Rust, you can use zbus for that.
While we released 8 beta releases for 2.0 in the last year, the API was not stable and hence many folks didn’t feel comfortable porting their code to 2.0 API. This is now fixed and folks are strongly encouraged to port their code to 2.0.
Our book has also been updated to reflect and demonstrate the new API and a new FAQ section has been added to it as well.
Do you really think it’s necessary to be so rude to make your point? Many people in the GNOME community know about zbus and especially D-Bus. I did actually edit my post immediately after to add description about zbus and D-Bus but seems somehow that was lost. I will try and add that info again now.
While 1.x release was well received, the lack of asynchronous API was the most requested feature. 2.0 API not only provides that but in fact the async API is now the primary one and blocking API is a convenience wrapper around it.
