Cian Butler

We then had to go through all the code base and find every place we imported JSON and replace it with orJSON.

And then we did these each incremental steps.

We didn't flip the switch.

We flipped the switch on the Django one first.

Then we went through and flipped the switch on updating all the JSON files one at a time.

Until I think one day I just got very bored, sat down and had a train ride and just banged through every single... I just grabbed everywhere we imported JSON library and just iterated through those files, making sure they were all correct.

Nice.

Like if you asked my previous employer if they're on Rust, they would say, nope, we have no Rust.

And I know for a fact there is Rust in every service because of the fact I put it there through that Python library.

And I think that's actually like a nice thing.

It's also true of the cryptography library in Python.

It's Rust based now.

There is Rust and there's Rust in Linux now.

Like Rust is everywhere.

It's getting rolled out everywhere.

But it's those nice places like or JSON where someone has sat down and said, how can I make this faster without breaking the API or in such a way that it doesn't take a massive lift to switch it out?

Yeah, not as often as I would like.

It's totally not as often as like, we've managed to get...

I talked about this before in previous talks at FOSDEM about our experience at it.

We switched or JSON first and it worked great.