metrics
too-many-lists
Our great sponsors
metrics | too-many-lists | |
---|---|---|
19 | 219 | |
70 | 3,011 | |
- | 1.8% | |
9.7 | 0.0 | |
4 days ago | about 1 month ago | |
Rust | ||
- | 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.
metrics
-
SQLx 0.7 released! Offline mode usability improvements, performance fixes and major upgrades across the board!
It's worth keeping an eye on Diesel's metrics suite (https://github.com/diesel-rs/metrics) as well; I found and fixed some suboptimal buffering that was affecting performance.
-
What's everyone working on this week (26/2023)?
See here for some numbers. The relevant code lives inside the diesel github repository. Please also keep in mind that these are just numbers and you should run those these on your own and also run tests with your actual work load.
-
Sqlx, diesel, orm or other sqlx query ?
Performance is worse than in comparable frameworks
-
Handle sessions and database requests
For the database part you might want to checkout a crate that's not based on sqlx as sqlx is known for providing non-optimal performance for the sqlite backend. rusqlite or diesel perform much better for this use case.
-
What ORM do you use?
No it will likely not be less performant. See these numbers for some benchmark results for numbers. (As always with benchmarks: Please don't trust my numbers. To be sure you need to do your own benchmarks with your own use-case)
-
Trying to learn by tutorials, for cannot find a single Actix/Diesel tutorial that actually compiles
See here for some benchmark results. The benchmarks itself are in the diesel repository. Otherwise I believe there are numbers in the techempower benchmarks as well, although that includes other factors .
-
Thoughts about switching from sqlx to tokio_postgres?
I'm developing a Rust web server backend in Axum that uses Postgres and performance will be pretty important since I plan to run it on one server for as long as possible. It seems like the postgres crate is about 2x faster than sqlx, and the postgres repository seems pretty active still.
-
Ormlite: An ORM in Rust for developers that love SQL
Congratulations to the release. I know all of this is hard work. I would like to invite you to submit a ormlite implementation to the diesel benchmark collection. As soon as that's merged you will get regular reports here. The relevant code is here in the diesel repository.
-
Rails developers write some Rust: a review of Axum 0.6
In that case you may be interested in the metrics for different database libraries. diesel is doing rather well at the moment. sqlx is in the middle of a large rewrite that should improve performance, so we'll see how it compares after that
-
Using Rust as my Backend
See here for some benchmark results for the diesel repository. Please keep in mind that as always with benchmarks, these numbers are not necessarily true for your usecase. Be sure to checkout at least the benchmark code and draw your own conclusions from there.
too-many-lists
-
Towards memory safety with ownership checks for C
You seem to have a preset opinion, and I'm not sure you are interested in re-evaluating it. So this is not written to change your mind.
I've developed production code in C, C++, Rust, and several other languages. And while like pretty much everything, there are situations where it's not a good fit, I find that the solutions tend to be the most robust and require the least post release debugging in Rust. That's my personal experience. It's not hard data. And yes occasionally it's annoying to please the compiler, and if there were no trait constraints or borrow rules, those instances would be easier. But way more often in my experience the compiler complained because my initial solution had problems I didn't realize before. So for me, these situations have been about going from building it the way I wanted to -> compiler tells me I didn't consider an edge case -> changing the implementation and or design to account for that edge case. Also using one example, where is Rust is notoriously hard and or un-ergonomic to use, and dismissing the entire language seems premature to me. For those that insist on learning Rust by implementing a linked list there is https://rust-unofficial.github.io/too-many-lists/.
-
Command Line Rust is a great book
Advent of Code was okay until I encounterd a problem that required a graph, tree or linked list to solve, where I hit a wall. Most coding exercises are similar--those requiring arrays and hashmaps and sets are okay, but complex data structures are a PITA. (There is an online course dedicated to linked lists in Rust but I couldn't grok it either). IMO you should simply skip problems that you can't solve with your current knowledge level and move on.
-
[Media] I'm comparing writing a double-linked list in C++ vs with Rust. The Rust implementation looks substantially more complex. Is this a bad example? (URL in the caption)
I feel obligated to point to the original cannon literature: https://rust-unofficial.github.io/too-many-lists/
-
Need review on my `remove()` implementation for singly linked lists
I started learning Rust and like how the compiler is fussy about things. My plan was to implement the data structures I knew, but I got stuck at the singly linked list's remove() method. I've read the book as well, but I have no clue how to simplify this further:
-
Factor is faster than Zig
My impression from the article is that Zig provides several different hashtables and not all of them are broken in this way.
This reminds me of Aria's comment in her Rust tutorial https://rust-unofficial.github.io/too-many-lists/ about failing to kill LinkedList. One philosophy (and the one Rust chose) for a stdlib is that this is only where things should live when they're so commonly needed that essentially everybody needs them either directly or to talk about. So, HashTable is needed by so much otherwise unrelated software that qualifies, BloomFilter, while it's real useful for some people, not so much. Aria cleaned out Rust's set of standard library containers before Rust 1.0, trying to keep only those most people would need. LinkedList isn't a good general purpose data structure, but, it was too popular and Aria was not able to remove it.
Having multiple hash tables feels like a win (they're optimized for different purposes) but may cost too much in terms of the necessary testing to ensure they all hit the quality you want.
-
Was Rust Worth It?
> Cyclic references can be dealt with runtime safety checks too - like Rc and Weak.
Indeed. Starting out with code sprinkled with Rc, Weak, RefCell, etc is perfectly fine and performance will probably not be worse than in any other safe languages. And if you do this, Rust is pretty close to those languages in ease of use for what are otherwise complex topics in Rust.
A good reference for different approaches is Learn Rust With Entirely Too Many Linked Lists https://rust-unofficial.github.io/too-many-lists/
- What are some of projects to start with for a beginner in rust but experienced in programming (ex: C++, Go, python) ?
-
How to start learning a systems language
Second, once you've finished something introductory like The Book, read Learning Rust With Entirely Too Many Linked Lists. It really helped me to understand what ownership and borrowing actually mean in practical terms. If you don't mind paying for learning materials, a lot of people recommend Programming Rust, Second Edition by Blandy, Orendorff, and Tindall as either a complement, follow-up, or alternative to The Book.
- My team might work with Rust! But I need good article recommendations
-
Conversion?
Learning Rust With Entirely Too Many Linked Lists which highlights a lot of the differences with how you need to structure your code in Rust compared to other languages.
What are some alternatives?
sea-orm - 🐚 An async & dynamic ORM for Rust
rust - Empowering everyone to build reliable and efficient software.
sea-query - 🔱 A dynamic SQL query builder for MySQL, Postgres and SQLite
Rustlings - :crab: Small exercises to get you used to reading and writing Rust code!
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
book - The Rust Programming Language
cornucopia - Generate type-checked Rust from your PostgreSQL.
CppCoreGuidelines - The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++
rust-postgis - postgis helper library.
easy_rust - Rust explained using easy English
const-eval - home for proposals in and around compile-time function evaluation
x11rb - X11 bindings for the rust programming language, similar to xcb being the X11 C bindings