rust-cfitsio
msquic


rust-cfitsio | msquic | |
---|---|---|
1 | 19 | |
40 | 4,158 | |
- | 1.3% | |
8.5 | 9.6 | |
9 days ago | 4 days ago | |
C | C | |
Apache License 2.0 | MIT License |
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.
rust-cfitsio
-
astro-rs: Attempting to port astropy to Rust
Yes, I should have mentioned one of the goals is pure Rust - I started in a Windows dev environment, and never could get projects like https://github.com/mindriot101/rust-fitsio to run natively; for now I’m hoping to maintain the cross-platform flexibility for this project, but I’ll definitely look into Marlu more, if it provides enough benefit, it’s easy enough to add that constraint
msquic
- Msquic: Cross-platform C implementation of QUIC protocol for C, C++, C#, Rust
-
Avoiding HTTP/3 (for a while) as a pragmatic default
I referred to sockets as an API design, not to express an opinion on whether you should place your protocol implementations inside or outside the kernel. (Although that’s undeniably an interesting question that by all rights should have been settled by now, but isn’t.)
Even then, I didn’t mean you should reproduce the Berkeley socket API verbatim (ZeroMQ-style); multiple streams per connection does not sound like a particularly good fit to it (although apparently people have managed to fit SCTP into it[1]?). I only meant that with the current mainstream libraries[2,3,4], establishing a QUIC connection and transmitting bytestreams or datagrams over it seems quite a bit more involved than performing the equivalent TCP actions using sockets.
[1] https://datatracker.ietf.org/doc/html/rfc6458
[2] https://quiche.googlesource.com/quiche
[3] https://github.com/microsoft/msquic
[4] https://github.com/litespeedtech/lsquic
-
My plan for making 256bit signed and unsigned integers in C. Please help me understand this concept better.
The documentation of MS QUIC says it is cross-platform, it should work on Linux, it has a CMake preset for Linux and you can download the prebuilt binary releases for Linux.
- Best performing quic implementation?
- Show HN: Protect Your CI/CD from SolarWinds-Type Attacks with This Agent
-
Least painful path to multiplatform builds?
https://github.com/microsoft/msquic (QUIC / HTTP3)
-
msquic VS MsQuic.Net - a user suggested alternative
2 projects | 15 Jul 2022
- The Illustrated QUIC Connection
- Msquic - Cross-platform, C implementation of the IETF QUIC protocol.
What are some alternatives?
astro-rust - Astronomical algorithms in Rust
mvfst - An implementation of the QUIC transport protocol.
rust-sun - A Rust library for calculating sun positions
lsquic - LiteSpeed QUIC and HTTP/3 Library
astro-rs - Astronomy utils written in Rust
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
swiss-ephemeris - Haskell bindings to the Swiss Ephemeris C library, bundles some basic ephemeris files.
quinn - Async-friendly QUIC implementation in Rust
star-charter - A command-line tool for producing vector-graphics charts of the night sky in SVG, PDF and PNG formats.
bitproto - The bit level data interchange format for serializing data structures (long term maintenance).
libremarkable - The only public framework for developing applications with native refresh support for Remarkable Tablet
openmptcprouter - OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt

