telepathy-qt
glommio
telepathy-qt | glommio | |
---|---|---|
8 | 29 | |
25 | 2,872 | |
- | 2.2% | |
0.0 | 7.6 | |
almost 2 years ago | 9 days ago | |
C++ | Rust | |
GNU Lesser General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
telepathy-qt
- The State of Async Rust
- Is there a unified client to use Matrix as well as traditional Messengers such as Telegram or Signal ?
- Is there a way you can have these "quick replies" for messenger apps on Ubuntu? I'd find it really handy...
- Telepathy – Real-time communication and collaboration for the desktop and mobile
-
Pidgin: The Universal Chat Client
Another FOSS universal chat solution that was probably better architected but unfortunately was never as popular as pidgin:
https://telepathy.freedesktop.org/
-
Throwback to the earliest of the GNOME Shell (GNOME 3) design iterations in 2008
They used Telepathy with Empathy as the client.
-
KDE Telegram Client? Meet Tok!
That's where we're now. Those free services are all (relatively) new and they still need to get some hang, but they have some enough that some kind and smart people were interested enough to develop a desktop client. Yes, in the ideal world (or at least my ideal world) people would just remembered about KDE-Telepathy and restart their work. I had some hope a couple years ago but definitely one man just can't keep up with the huge amount of work it needs, not just in KDE-Telepathy but in upstream Telepathy. Hell, it's a miracle that things like Telegram-Qt still move, albeit very slow.
glommio
-
I want to share my latest hobby project, dbeel: A distributed thread-per-core nosql db written in rust
I used glommio as the async executor (instead of something like tokio), and it is wonderful. For people wondering whether it's "good enough" or to use C++ and seastar (as I have thought about a lot before starting this project), take the leap of faith, it's fast - both in terms of run time and to code.
-
The State of Async Rust
My understanding is you always need a runtime, somethings needs to drive the async flow. But there are others on the market, just not without the.. market domination... of tokio.
https://github.com/smol-rs/smol looks promising simply for being minimal
https://github.com/bytedance/monoio looks potentially easier to work with than tokio
https://github.com/DataDog/glommio is built around linux io_uring and seems somewhat promising for performance reasons.
I haven't played with any of these yet, because Tokio is unfortunately the path of least resistance. And a bit viral in how it's infected tings.
-
Learning Async Rust with Too Many Web Servers
I think you missed one which is based on io_uring [1].
In my benchmarks with a slightly tweaked version it was 2x faster than Nginx and and 30x faster than Python's SimpleHttpServer.
[1] https://github.com/DataDog/glommio/blob/master/examples/hype...
-
How much reason is there to be multi-threaded in the k8s environment
b) It's proven now e.g Seastar, Glommio that the fastest way to run a multi-threaded application is to have one instance with one thread pinned per CPU core. Then to have fibers/lightweight threads on top handling all of the asynchronous code. Your approach of lots of instances is the slowest so there will be a ton of unnecessary thread context-switching.
-
Why does Actix-web's handler not require Send?
I assume Tokio itself, see e.g monoio or glommio, but also Seastar for C++.
-
How does async Rust work
https://github.com/DataDog/glommio Rust thread per core library.
-
Use io_uring for network I/O
> Few of us have really figured out io_uring. But that doesn't mean it is slower.
seastar.io is a high level framework that I believe has "figured out" io_uring, with additional caveats the framework imposes (which is honestly freeing).
Additionally the rust equivalent: https://github.com/DataDog/glommio
-
Is async runtime (Tokio) overhead significant for a "real-time" video stream server?
This use case is perfect for https://github.com/DataDog/glommio which is a thread-per-core runtime that is appropriate for latency sensitive code.
-
Blessed.rs – An unofficial guide to the Rust ecosystem
It's worth mentioning: Under "Async Executors", for "io_uring" there is only "Glommio"
I recently found out that ByteDance has a competitor library which supposedly has better performance:
https://github.com/bytedance/monoio
https://github.com/DataDog/glommio/issues/554
-
Building a High-Performance DB Buffer Pool in Zig W\ Io_uring New Fixed-Buffers
FYI, Datadog has a Rust library for scheduling things to run thread-per-core with io_uring
It'd be really useful for DB use cases:
https://github.com/DataDog/glommio
What are some alternatives?
purple-facebook - Facebook protocol plugin for libpurple (moved from jgeboski/purple-facebook)
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
franz - Franz is a free messaging app for services like WhatsApp, Slack, Messenger and many more.
tokio-uring - An io_uring backed runtime for Rust
telegram-qt - Qt-based library for Telegram network
Seastar - High performance server-side application framework
flameshot - Powerful yet simple to use screenshot software :desktop_computer: :camera_flash:
monoio - Rust async runtime based on io-uring.
purple-discord - A libpurple/Pidgin plugin for Discord
MIO - Metal I/O library for Rust.
website - Website for the Tokio project
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.