Cian Butler

I did a very big bump on some stuff recently, and we're testing out a new framework for writing parts of our Edge code on Rust.

And it went from version 0.6 to 0.7.

And I think it just added a lot of optional args to a lot of stuff.

So we had to read the docs and add those optional args.

That was not a big change.

It took maybe an hour of my time to just do that.

And that was fine.

And in saying that, it came with improvements.

It came with cache improvements and all that kind of stuff.

So taking in those changes was good.

It's obviously feature changes, not bug fixes.

So I'm happy to take that stuff in.

But when I...

We're trying out more Rust and I'm bringing more people in to look at Rust who are coming from a Python world and coming from different worlds.

And they look at a lock file and they say, why are none of these things stable?

I have to have that conversation with them about why we're still using pre-release software and why it might be years before that pre-release software comes in.

And I don't think it's a problem you need to fix, but maybe it's a problem of education.

And how do we talk about the V0 of packages to make people understand that this is, should this be production or should this not be production?

It's not, a V1 isn't a signal that this should be production or not.

It's just a signal of stability of the API.