kerkour.com
cuprate
| kerkour.com | cuprate | |
|---|---|---|
| 2 | 2 | |
| 456 | 101 | |
| 0.0% | 6.9% | |
| 4.5 | 9.1 | |
| 2 months ago | 2 days ago | |
| Rust | Rust | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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.
kerkour.com
-
SQL and Rust
There are plenty: - diesel - famous example of what the Rust type system can get you beyond just "memory safety". My go-to choice for most projects. Having autocomplete for my database DSL is something I find it hard to go without. But it comes at a fairly high cost of confusing, generic-heavy code. - sqlx - also a very solid choice. You write SQL queries, which are optionally checked against a database instance at compile-time. A downside I've heard repeated a lot (by some fairly reputably figures) is that sqlx adds a fairly significant overhead to queries, and according to this issue is 7-70x slower than diesel. If the performance of your database is important to you, run some benchmarks and see if it's an issue - seaorm - a relatively new ORM, and I haven't used it much, but my initial impressions were that it was a little too "magic". Maybe it just reminded me too much of Spring Boot. I'm not sure. It's probably a totally fine library - postgres (or equivalent) - you can always just skip the ORM and use the database driver directly. Pretty nice for smaller projects, but totally viable for big projects too. Just a matter of personal preference
-
How to implement worker pools in Rust
As usual, you can find the code on GitHub: github.com/skerkour/kerkour.com (please don't forget to star the repo 🙏).
cuprate
-
Looking for a reason why my syncing is abnormally slow
from cuprate.github.io:
-
[Cuprate] 2 months later and the quest for documentation
I announced the project the 8th of February and I'm very excited to report our progress for Monero Birthday🎂. A reminder: Cuprate is an upcoming, experimental, modern and secure Monero node, written in Rust. This project is currently the only planed alternative implementation for Monero, and we hope to bring numerous improvements that'll help people and the Monero network. Learn more on https://github.com/Cuprate/cuprate This is the first time we report our progress, and we hope to keep a bimonthly report for the community. And now let's make some place for the big news:
What are some alternatives?
shisho - Lightweight static analyzer for several programming languages
entrusted - Sanitize documents to safe PDFs, for active content removal
binserve - A fast production-ready static web server with TLS (HTTPS), routing, hot reloading, caching, templating, and security in a single-binary you can set up with zero code.
nim-monero-rpc - Nim library for interacting with Monero wallets & nodes via RPC.
sandwich - Sandwich is a multi-platform, multi-language, open-source library that provides a simple unified API for developers to use (multiple) cryptographic libraries in their applications.
mithril - Pure Rust Monero Miner
tangram - Tangram makes it easy for programmers to train, deploy, and monitor machine learning models.
aquatic - High-performance open BitTorrent tracker (UDP, HTTP, WebTorrent)
myblog - Personal blog written in Rust, using salvo and sqlx
itchysats - CFDs on Bitcoin.
hypercube - HyperCube is a revolutionary, high-performance decentralized computing platform. HyperCube has powerful computing capabilities to provide high-performance computing power and large-scale data storage support for VR, AR, Metaverse, Artificial Intelligence, Big Data, and Financial Applications.🛰