We Didn't Pick Rust(floedb.ai)
floedb.ai
We Didn't Pick Rust
https://floedb.ai/blog/rust-quarkus-c
5 comments
On the company about page:
We work in Rust, Java/Quarkus, C, C++, LLVM and Python ...
?
We work in Rust, Java/Quarkus, C, C++, LLVM and Python ...
?
Fair question. Outside of a few prototypes and experiments, we don’t really use Rust in production (yet).
The company as a whole uses a pretty wide range of languages, but for this project the baseline was Java/Quarkus. The discussion wasn’t “are we allowed to use Rust?”, but whether bringing it in for this new component made sense given team ownership, ops, and how early the project still was.
The company as a whole uses a pretty wide range of languages, but for this project the baseline was Java/Quarkus. The discussion wasn’t “are we allowed to use Rust?”, but whether bringing it in for this new component made sense given team ownership, ops, and how early the project still was.
TLDR: we didn't pick rust because we're a Java shop.
Java was the baseline for this project, yes. The post is really about how we looked at the trade-offs, not about locking in a language choice forever.
For what it’s worth, the team isn’t Java-only either: some of us have spent a lot of time in C or C++ before, and others were already very comfortable with Java. The question here was mostly whether bringing in a new production language made sense at that stage of the project.
For what it’s worth, the team isn’t Java-only either: some of us have spent a lot of time in C or C++ before, and others were already very comfortable with Java. The question here was mostly whether bringing in a new production language made sense at that stage of the project.
This came from a real decision we had to make while building a new startup inside an existing company. It’s less about Rust itself and more about how those decisions actually play out.
We tried Rust in a few small places to make the trade-offs clearer. Happy to expand if useful.