teensy4-rs
msquic
| teensy4-rs | msquic | |
|---|---|---|
| 2 | 19 | |
| 317 | 4,225 | |
| 2.2% | 2.0% | |
| 5.7 | 9.6 | |
| 24 days ago | 6 days ago | |
| Rust | 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.
teensy4-rs
-
MCU recommendation
the nRF line is very well supported by Rust, but you'd have to get a canbus breakout since the nrf line doesn't support canbus out of the box. An alternative is the teensy line of MCUs - the higher-end models have CAN built in and there's decent Rust support. https://github.com/mciantyre/teensy4-rs
-
How is it possible to program Teensy boards without <Arduino.h>?
The most complete teensy environment I could find that isn't Arduino is this: https://github.com/mciantyre/teensy4-rs which is Rust not C.
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?
ccextractor - CCExtractor - Official version maintained by the core team
mvfst - An implementation of the QUIC transport protocol.
libremarkable - The only public framework for developing applications with native refresh support for Remarkable Tablet
lsquic - LiteSpeed QUIC and HTTP/3 Library
Themis - Easy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3