quinn
windows-rs
Our great sponsors
quinn | windows-rs | |
---|---|---|
23 | 97 | |
3,449 | 9,812 | |
2.7% | 3.2% | |
9.0 | 7.7 | |
7 days ago | 6 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
quinn
-
Why HTTP/3 is eating the world
Since it lives on top of UDP, I believe all you need is SOCK_DGRAM, right? The rest of QUIC can be in a userspace library ergonomically designed for your programming language e.g. https://github.com/quinn-rs/quinn - and can interoperate with others who have made different choices.
Alternately, if you need even higher performance, DPDK gives the abstractions you'd need; see e.g. https://dl.acm.org/doi/abs/10.1145/3565477.3569154 on performance characteristics.
-
Async rust – are we doing it all wrong?
> Making things thread safe for runtime-agnostic utilities like WebSocket is yet another price we pay for making everything multi-threaded by default. The standard way of doing what I'm doing in my code above would be to spawn one of the loops on a separate background task, which could land on a separate thread, meaning we must do all that synchronization to manage reading and writing to a socket from different threads for no good reason.
Why so? Libraries like quinn[1] define "no IO" crate to define runtime-agnostic protocol implementation. In this way we won't suffer by forcing ourselves using synchronization primitives.
Also, IMO it's relatively easy to use Send-bounded future in non-Send(i.o.w. single-threaded) runtime environment, but it's almost impossible to do opposite. Ecosystem users can freely use single threaded async runtime, but ecosystem providers should not. If you want every users to only use single threaded runtime, it's a major loss for the Rust ecosystem.
Typechecked Send/Sync bounds are one of the holy grails that Rust provides. Albeit it's overkill to use multithreaded async runtimes for most users, we should not abandon them because it opens an opportunity for high-end users who might seek Rust for their high-performance backends.
[1]: https://github.com/quinn-rs/quinn
-
quicssh-rs Rust implementation SSH over Quic proxy tool
quicssh-rs is quicssh rust implementation. It is based on quinn and tokio
-
The birth of a package manager [written in Rust :)]
Regarding Quinn, I had a blast this week resurrecting an old PR. Looking forward to the next!
- Best performing quic implementation?
-
str0m a sans I/O WebRTC library
By studying u/djcu/hachyderm.io (and others!) excellent work in Quinn, doing a sans I/O implementation of QUIC https://github.com/quinn-rs/quinn we have a way forward.
-
durian - a high-level general purpose client/server networking library
QUIC isn't web/wasm-compatible because of https://github.com/quinn-rs/quinn/issues/1388, so durian wouldn't either since it's built on top of it.
-
FPS server with QUINN?
Quinn, as in the implementation of QUIC? https://github.com/quinn-rs/quinn
-
I built a Zoom clone 100% IN RUST
You are right, I am planning to switch the transport to UDP + quic using the awesome QUINN library, https://github.com/quinn-rs/quinn .
-
I write a secure UDP tunnel
Hi, I am new to the community, I just started learning rust and created a secure UDP tunnel based on the Quinn library, thanks to Quinn, I didn't need to go into the detail of the QUIC protocol and quickly created a UDP tunnel, and thanks to the BBR congestion control algorithm it uses, the tunnel performs quite well with lousy and long fat network, I didn't do any benchmark, but it performs a lot better (higher throughput with LFN) than most of other TCP tunnel implementations I used before.
windows-rs
-
Ask HN: What is the best way to build a desktop app in Windows in 2023?
It's a shame that, unlike with Win32, using WinUI places pretty harsh restrictions on which programming languages and environments you can use. Only C# and C++ are supported, the latter only with Microsoft compilers. For everything else, including Rust[1], Python and MinGW C/C++, there is no answer for OP's question, and the effect of this on the visual consistency of the Windows desktop is obvious - there is none. Every third-party app uses a different toolkit with a different look and feel, because the library providing the standard look and feel simply isn't available to the majority of developers.
[1]: https://github.com/microsoft/windows-rs/pull/1836
-
Good rust book for the 1st time programmer with no prior programming experience?
[0] https://github.com/microsoft/windows-rs
-
What in Rust is equivalent to C++ DLLs (shared libraries), or what do I need to do to support extensions in my app?
On Windows you'd need to call the LoadLibraryEx method. You'd also need a crate to call Win32 functions, I suggest windows-rs.
-
Microsoft is to enable Rust use for Windows 11 kernel
windows-rs, Microsoft's crate wrapping the Windows API, already includes the WDK, the special sdk for creating kernel code.
-
Which GUI toolkit for Rust today.. few questions...
On windows, I'll probably use https://github.com/gabdube/native-windows-gui or https://github.com/microsoft/windows-rs both of them seem pretty solid.
-
Which crate for listing / moving Windows 11 windows ?
*nod* It's an official Microsoft thing generated from official Microsoft API definition files. (The repo is at microsoft/windows-rs on GitHub.)
-
Kernel Headers for Windows could soon make it into windows-rs
Microsoft offers official "bindings" to Win32 APIs through win32metadata. However, until recently, it did not include metadata for kernel-level functions or WDK. In early 2021, an issue was raised through windows-rs regarding this limitation, but progress was slow until now. Microsoft has finally released official metadata for WDK, which can be found on the wdkmetadata repository. The latest comment on the issue thread can be found here:
-
Is the Rust ecosystem capable of making a cross-platform mobile game with p2p Bluetooth yet?
Is something wrong with https://github.com/deviceplug/btleplug or you haven't found it? You could also use bindings to platform libraries like https://github.com/microsoft/windows-rs and https://github.com/rust-mobile/ndk if btleplug doesn't have something fundamental to you.
- A brief interview with Tcl creator John Ousterhout
What are some alternatives?
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
winapi-rs - Rust bindings to Windows API
s2n-quic - An implementation of the IETF QUIC protocol
Cargo - The Rust package manager
h3
fltk-rs - Rust bindings for the FLTK GUI library.
msquic - Cross-platform, C implementation of the IETF QUIC protocol, exposed to C, C++, C# and Rust.
slint - Slint is a declarative GUI toolkit to build native user interfaces for Rust, C++, or JavaScript apps.
laminar - A simple semi-reliable UDP protocol for multiplayer games
Slint - Slint is a toolkit to efficiently develop fluid graphical user interfaces for any display: embedded devices and desktop applications. We support multiple programming languages, such as Rust, C++ or JavaScript. [Moved to: https://github.com/slint-ui/slint]
neqo - Neqo, an implementation of QUIC in Rust
maven-mvnd - Apache Maven Daemon