Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev. Learn more →
Trust-dns Alternatives
Similar projects and alternatives to trust-dns
-
-
citybound
A work-in-progress, open-source, multi-player city simulation game.
-
InfluxDB
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
-
woodpecker
Drill is an HTTP load testing application written in Rust (by fcsonline)
-
-
tauri
Build smaller, faster, and more secure desktop applications with a web frontend.
-
-
Onboard AI
Learn any GitHub repo in 59 seconds. Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev.
-
-
MeiliSearch
A lightning-fast search engine that fits effortlessly into your apps, websites, and workflow.
-
-
-
Symphonia
Pure Rust multimedia format demuxing, tag reading, and audio decoding library
-
-
-
-
-
Nebula
A scalable overlay networking tool with a focus on performance, simplicity and security
-
-
rust-gpu
🐉 Making Rust a first-class language and ecosystem for GPU shaders 🚧
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
trust-dns reviews and mentions
-
You might want async in your project
IO is not a part of the async runtime contract (I don't know if this is good or bad), and Tokio & futures famously have different `Async{Read,Write}` traits. I once had to do this [0] to adapt between them.
This means that any crate that uses IO will be bound to a limited number of Runtimes. Everything being Tokio-only is pretty bad (though Tokio itself is great), but here we are...
[0] https://github.com/bluejekyll/trust-dns/pull/1373#issuecomme...
-
What would you rewrite in Rust?
You might be interested in Trust DNS - "A Rust based DNS client, server, and Resolver, built to be safe and secure from the ground up."
-
Announcing `async-dns`
It looks like you need to reach for a separate crate for that: https://github.com/bluejekyll/trust-dns/blob/7dcb7b983f5407d95d93b800af13caeee975aaa8/crates/async-std-resolver/src/lib.rs
This is not true; you can use the async resolver with other executors: https://github.com/bluejekyll/trust-dns/blob/main/crates/resolver/src/async_resolver.rs
-
Innernet: Open source Rust based Tailscale alternative by Tonari
You could run a local DNS server using something like https://github.com/bluejekyll/trust-dns . Or, you could install an NSS module to resolve names via the innernet client.
-
single-producer single-consumer concurrent queue
My point is that "implementation that doesn't use unsafe" is not necessarily always slower than "implementation that does use unsafe". Often people assume that this is the case, and it isn't. tinyvec currently beats smallvec in more than a few benchmarks. Not all, but some. And this sometimes visible to users. The point is that if you want speed, you don't necessarily need to give up any safety at all. Most differences in performance are due to the amount of effort or expertise that has been spent on the codebase, not the amount of unsafe in it.
-
A note from our sponsor - Onboard AI
getonboard.dev | 9 Dec 2023
Stats
bluejekyll/trust-dns is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of trust-dns is Rust.