semver-trick
Thruster
semver-trick | Thruster | |
---|---|---|
15 | 8 | |
414 | 1,052 | |
- | 1.2% | |
2.8 | 5.6 | |
25 days ago | about 2 months ago | |
Rust | Rust | |
Apache License 2.0 | 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.
semver-trick
-
Making Rust supply chain attacks harder with Cackle
Let's say crate B depends on crate A with a pinned dependency, and uses one of its types in a public interface.
Crate C depends on them both. It now can't bring in updates to A until B does, and when B updates that's a breaking change, so it better bump its major version.
Take a look at this teick, for example, for foundational crates updating their major version: https://github.com/dtolnay/semver-trick
Now imagine that being an issue every single patxh update.
-
The module system is too confusing
Rust modules require a tiny bit more definition up-front, but they neatly decouple the module hierarchy from file layout so you can reorganize code however you like in future, and they support very fine grained control of privacy (such as being able to say pub(super) and pub(crate)). In extreme cases, you can even re-export symbols from one module in another without it counting as a breaking change, so you have even more options for evolving your project without breaking existing consumers. Look at the the semver trick as an example of how powerful this can be and how much freedom it gives library implementors. (And even if you're only a library consumer, wouldn't you rather be consuming libraries by implementors that had more freedom and power?)
-
My first year with Rust: The good, the bad, the ugly
A library author concerned about this can use the semver trick. TL;DR: if your current version is 0.42, you can do a 1.0 release, then do a 0.43 release that depends upon your 1.0 release and re-exports all the symbols.
-
Does Rust have any design mistakes?
I mean for all the parts of the standard library that do not change, one could presumably use the semver-trick.
-
Rust is hard, or: The misery of mainstream programming
The semver trick can help with libraries at least when they go to unify the ecosystem. Release new versions that replicate previous APIs in a compatible way while moving to the standard library implementation.
-
Roadmap
Because you still run into the problem that's been seen when various important crates upgraded and either didn't use the semver trick or had downstream crates specifying Cargo.toml version requirements too narrowly for it to be effective.
- The Rust SemVer Trick (2019)
-
This Year in Embedded Rust: 2021 edition
It's called the "semver-trick" [1].
[1]: https://github.com/dtolnay/semver-trick
- The Semver Trick
-
The chip shortage keeps getting worse. Why can't we just make more?
The JVM is 114MiB on my machine. A near-minimal ggez program in debug mode is about 100MiB,¹ and ggez is small for a Rust application library. When you start getting into the 300s of dependencies (i.e. every time I've ever got beyond a trivial desktop application), you're lucky if your release build is less than 100MiB.
Sure, I could probably halve that by forking every dependency so they aren't duplicating versions, but that's a lot of work. (It's a shame Rust doesn't let you do conditional compilation based on dependency versions, or this would be a lot easier. As it is, we have to resort to the Semver trick: https://github.com/dtolnay/semver-trick/ — not that many people do that, so it's functionally useless.)
¹: I can get it down to around 8MiB with release mode, lto etc., but that significantly increases the build time and only about halves the weight of the intermediate build files.
Thruster
- Thruster Web Server Framework 2023 Roadmap (because one whole person on reddit asked for it)
-
shuttle v0.7.1 has been released (improved isolation, new supported frameworks, QOL improvements)
We've added support for the warp, salvo & thruster frameworks
-
Rust is hard, or: The misery of mainstream programming
Maybe, or maybe not, interestingly, I had to store async functions that call other arbitrary async functions for thruster. I tried many of the things posed in the article, and eventually ended up doing something similar to how bevy works -- that is, I made a bunch of tuples.
-
What is the best web backend framework for a big project ?
For a quick self promo, I've used thruster (https://github.com/thruster-rs/Thruster) for a few side projects with 10k reqs/day or so and I love it to death coming from nodejs land
-
Rust pros and cons vs e.g. nodejs
Now for my shameless plug; I use a framework primarily that I maintain that aims to have the ergonomics of express or koa in rust. Try it out if you're interested: thruster.
- thruster v1.1.10: Adding "strict mode" and actix-web as a backend
-
Thruster 1.1.2 Release - An express-like HTTP server in Rust
If you'd rather wait for the next release (it'll be more like this afternoon rather than a year from now, promise!) I just fixed it in a PR here
What are some alternatives?
lang-team - Home of the Rust lang team
rocket-auth-login - Authentication and login processing for Rust's Rocket web framework. Demonstrates a working example of how to authenticate users and process login as well as how to handle logging out.
cargo-llvm-lines - Count lines of LLVM IR per generic function
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
rust-base64 - base64, in rust
feroxbuster - A fast, simple, recursive content discovery tool written in Rust.
rust-quiz - Medium to hard Rust questions with explanations
hello-world.rs - 🚀Memory safe, blazing fast, configurable, minimal hello world written in rust(🚀) in a few lines of code with few(1092🚀) dependencies🚀
serde - Serialization framework for Rust
yew - Rust / Wasm framework for creating reliable and efficient web applications
driver-examples - Rust example programs for many of my hardware device drivers running on STM32F3 Discovery, STM32F103 "Blue Pill", RaspberryPi and micro:bit boards
Rocket - A web framework for Rust.