rust-djangohashers
autocxx
Our great sponsors
rust-djangohashers | autocxx | |
---|---|---|
1 | 17 | |
55 | 2,038 | |
- | 2.0% | |
5.4 | 7.7 | |
about 2 months ago | about 1 month ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | 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.
rust-djangohashers
-
What's your favourite under-rated Rust crate and why?
A crate that's kind of similar use-case-wise is djangohashers, which I've used to handle some interfacing with old legacy Django installations I've handled.
autocxx
-
How do you feel about comments made by Tim Sweeney?
Meanwhile, one of the best C++ sources which community mostly think of - Chromium - starting to experience with Rust. If i'm not mistaken using https://github.com/google/autocxx
-
The Val Object Model : Dave Abrahams, Sean Parent, Dimitri Racordon, David Sankel
There's bindgen, cxx and autocxx. Obviously not as convenient as C++ calling C++; the more you need to interoperate with C++ code the more it makes sense to just stay with C++.
-
Are we reference yet? C++ references in Rust
If you want to reach the author for a correction, perhaps leave a comment on the Medium post or perhaps mention it on the autocxx PR I found this article from.
-
The Unicode Consortium announces ICU4X 1.0, its new high-performance internationalization library. It's written in Rust, with official C++ and JavaScript wrappers available.
Rust and C++ are not directly interoperable, but you can try to use some fancy libraries if your C++ codebase is simple. Google is taking on this gargantuan task with autocxx. I believe it is related to their exploration efforts to bring Rust to Chrome.
-
Mark Russinovich (Azure CTO): "it's time to halt starting any new projects in C/C++ and use Rust"
I used autocxx in a recent project and was amazed at how easy it was to call into C++ -- Rust Analyzer was even able to provide completion hints.
-
The State Of Rust In 2022 – De Programmatica Ipsum
Sure, they can improve C++ interop - and they have been - but that doesn't help them maintain the dozens of millions of lines of C++ they (Google, and others) currently have. Carbon is a pragmatic solution to the state of affairs in C++ that doesn't require them to rewrite all of their existing code to improve its maintainability.
-
Programming languages endorsed for server-side use at Meta
The areas you mentioned (CLI, web services, low level systems programming) are not mutually exclusive. Doing a good job on one doesn't mean something else is affected.
The folks who worked on the most popular command line argument parser (https://docs.rs/clap/latest/clap/#example) made a positive contribution that didn't detract from any other use case.
Similarly, the folks working on improving Rust for web services will also make it better for systems programming. In a blog post published today (https://blog.rust-lang.org/inside-rust/2022/07/27/keyword-ge...), they discuss keyword generics, a feature that will be equally helpful for `async` code and `const` functions evaluated at compile time.
There is already some interoperability with C++ (http://cxx.rs) and ongoing research into automating this interoperability (https://github.com/google/autocxx, https://github.com/google/crubit). Feels like there's enough effort
-
Google brands Carbon language as an 'experimental successor to C++'
That's not at all in Rust's bill, it needs an interaction layer to talk to C++. Efforts like cxx (and google's own autocxx) try to make this layer more automated and less painful, but the layer is still there, it still has a cost, and it doesn't erase the impedance mismatches between the languages.
-
Carbon Language: An experimental successor to C++
Notably Google is also investing in autocxx to make C++/Rust bidirectional interoperation easier
-
Carbon - an experimental C++ successor language
Again, not really...? A lot of the proposed ABI changes (for C++ - I don't know what they're planning for Carbon) are trivial to automatically fix if you have source access. If you don't have source access, you "only" need to maintain the ABI at the boundaries between foreign code and your code, which is quite possible (especially after the success of autocxx and related projects in the Rust <-> C++ world)
What are some alternatives?
orion - Usable, easy and safe pure-Rust crypto [Moved to: https://github.com/orion-rs/orion]
cxx - Safe interop between Rust and C++
rust-security-framework - Bindings to the macOS Security.framework
rust-bindgen - Automatically generates Rust FFI bindings to C (and some C++) libraries.
ed25519-dalek - Fast and efficient ed25519 signing and verification in Rust.
TIC-80 - TIC-80 is a fantasy computer for making, playing and sharing tiny games.
schannel-rs - Schannel API-bindings for rust (provides an interface for native SSL/TLS using windows APIs)
gdnative - Rust bindings for Godot 3
octavo - Highly modular & configurable hash & crypto library
carbon-lang - Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
webpki - WebPKI X.509 Certificate Validation in Rust
jakt - The Jakt Programming Language