-
turso
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
Dec 10, 2024 : "Introducing Limbo: A complete rewrite of SQLite in Rust"
https://turso.tech/blog/introducing-limbo-a-complete-rewrite...
Jan 21, 2025 - "We will rewrite SQLite. And we are going all-in"
https://turso.tech/blog/we-will-rewrite-sqlite-and-we-are-go...
Project: https://github.com/tursodatabase/turso
Status: "Turso Database is currently under heavy development and is not ready for production use."
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
For slices the access is handled inside of the compiler: https://github.com/rust-lang/rust/blob/235a4c083eb2a2bfe8779...
Array access is const due to the known length of the array.
-
> One good reason is that people have written golang adapters, so that you can use sqlite databases without cgo.
There's also the Go-wrapped WASM build of the C sqlite[0] which is handy.
[0] https://github.com/ncruces/go-sqlite3
-
rqlite
The lightweight, fault-tolerant database built on SQLite. Designed to keep your data highly available with minimal effort.
rqlite[1] author here. Just to be clear, rqlite is not SQLite but written in Go. rqlite uses the vanilla C code, and calls it from Go. I consider that an important advantage over other approaches -- rqlite gets all the benefits of rock-solid[2] SQLite. There are no questions about the database engine.
[1] https://rqlite.io
[2] https://www.sqlite.org/testing.html
-
except that if you read into the actual issue you will realize that transposing matrices high performant is surprisingly not trivial, e.g. see this non trivial code: https://github.com/ejmahler/transpose/blob/e70dd159f1881d86a...
furthermore the issue at core was an integer overflow, which is tricky and e.g. has poppet up on HN recently in context of "proven correct" code still having bugs (because the prove didn't use finit precision integers)
and in that context rust does check for integer overflow during debug build by default and companies do sometimes enable it even on release mode for security sensitive code(1), sure you probably can explicitly opt-in to it in C too, but either way it's more likely for you to find such bugs in rust then in C due to test normally running with overflow checks enabled
so if anything the linked issue is in favor of using rust over C while reminding you that no solution is perfect
(1): It comes at a high performance cost, but sometimes for some things it's an acceptable cost. Also you can change such setting per crate. E.g. at a company I worked at a few years ago we did build some sensitive and iffy but not hot parts always with such checks enabled and some supper hot ML parts always with optimizations enabled even for "debug/test" builds.
-
"The Silver Searcher" is a program written in the _same_ "unsafe" language as grep
This is obviously not analogous to Rust evangelism that targets projects written in C
The author claims the program is a clone of ack; ack is written in a "safe" language
https://geoff.greer.fm/ag/
https://beyondgrep.com/
-
"The Silver Searcher" is a program written in the _same_ "unsafe" language as grep
This is obviously not analogous to Rust evangelism that targets projects written in C
The author claims the program is a clone of ack; ack is written in a "safe" language
https://geoff.greer.fm/ag/
https://beyondgrep.com/