2 min
Rust 2020: Funding
👋 This page was last updated ~5 years ago. Just so you know.
Blog posts that praise Rust are many but funding is generally in short supply.
If even a small percentage of the money Rust saves companies was put back into the ecosystem it would help secure the future of the platform tremendously.
Multiple sources of funding
It is unreasonable going forward to expect the same handful of companies to provide all the funding.
Although Rust was born (or so I’m told) at Mozilla, it seems pretty clear that it has outgrown it significantly, and many big companies now benefit from Rust.
I hope they not only contribute code in the future but also funding.
Funding even if you don’t ask for it
Projects like rust-analyzer cost money, they explained in great
detail. Those
should be funded.
Other projects have not explained it in great detail but nevertheless could use funding as well.
There are many people good at what they do but not especially good at getting funding. This doesn’t mean they shouldn’t get funding.
Goodwill does not pay the rent
If we want the wonderful folks who have been improving all aspects of the compiler, various libraries, infrastructure, docs, and I’m forgetting many, to stay and be happy and not burn out and leave for high-paying jobs, we need funding.
Being well-compensated (or even compensated at all) for work on open-source projects, does not make the work any less noble or open source.
Funding
Thanks for funding.
Here's another article just for you:
Recursive iterators in Rust
7 min
I’ve been looking for this blog post everywhere, but it doesn’t exist, so I guess it’s my turn to write about Some Fun with Rust.
The task at hand
Let’s say you have a recursive, acyclic data structure, like so:
struct Node {
values: Vec<i32>,
children: Vec<Node>,
}
This allows you to represent a tree-like structure:
[1, 2, 3]
/\
/ \
/ \
/ \
/ \
[4, 5] [6, 7]