Is everyone excited for this next talk?
Yeah, I am.
All right.
So, the semester is here to tell us about court eutails in a bunch of and how far.
Thank you.
Hello everyone.
So, first I'd like to start by saying that I'm not the employee.
It's not a material project and I've been a deviant developer for the last 20 years.
And I love reading what people have been telling about modia and deviant and Firefox and this project.
So, I have a PhD in reading those 12s.
What are the courtyles?
So, who doesn't know what it is in that room?
One person, I think, is a joke.
So, the first implementation is much older than many of us.
If you look at the sort of the first unique, you will see an implementation in assembly.
The second version in 72, what in see and the code is pretty similar and the usage and the interface is pretty similar to what you see currently in the very simple implementation.
So, when you think about it, 50, 60 years after, we are still using what those folks did a long time ago.
So, you know those comments.
I'm not going to ask you if you know those comments.
It would be an insult in that room.
That one, the position that you know all of you, you know the first two.
So, the last one, over the usage, it almost is for it's Linux.
Next is video, who uses that comment in that room?
And over it.
Who knows what this stack?
Oh, a few people.
You are crazy guys.
And the last one, PR.
I don't know anyone who uses that one in real life.
It's for printing.
It is one of the comments where we still have work to do, but as nobody raise their hand in the room.
So, we have more than one and a red comment in that project.
I did two presentations on that stuff.
Way more technical than the one I'm going to do right now because I want to focus on the human aspect of making those kind of changes and not really on the technical level.
So, if you care about technical implementation, you will see me talking with the same accent three years ago and last year about those projects.
But basically, the TLDR of what I presented and what we see is that it is first a super interesting project.
We are all gigs.
We love to create new stuff.
Why do we do it?
Sometimes we don't have a good reason.
Just learning something for me to ask COVID.
We were bought at home in France and I think in many countries in Europe.
So, I want to learn the rest.
I have been a Brazilian employee.
I know many of the folks who created that language.
So, I want to learn it.
And why not carry it?
Because see sucks.
So, I'm going to throw a bit because I understood that this is a pre-firement.
I think that see the language of the past.
I think the new generations that I don't want to learn see.
When I was at the university, it was a school ball.
And fourth round.
And now for me, I think that the next generation is going to sing the same.
About see that I did about COVID and fourth round.
This claimer is not about license.
I don't want to talk about M.A.T.
That is not the debate that is interesting to me.
I know that some people are very passionate about that.
But I'm not as long as it is a debyan compliant.
I'm happy.
And the rest is amazing for plenty of things.
And I will go back to that in the next slide.
So, a few months ago,
John, the VP of Canonical approached me saying,
oh, we want to evaluate your tool for the next release.
Full disclosure.
Also discussed with Max.
Total worth a few years ago about it.
And they published a blog post after discussing together.
And we have been coordinating closely for the last six or seven months
on that project with people who have been also debyan developers
for people that I know from the community.
Canonical is really trying to focus on what matters.
And this project is really a great step to show that you can do this kind of thing.
So taking a piece of software that has been exact,
that has been shipping on software for like 20 years.
And still being relevant and still works.
But we want to show that.
And we don't want to be right everything in the window that makes no sense.
It's not a rest everywhere.
It is being deliberate.
So with Canonical, it's started with that project and pseudo.
And there are also evaluating the pieces of software,
especially unsafe software that I've been existing in Linux before for a long time.
So we want to do also a great deal in production.
So we did that not in the latest LTS of Ubuntu,
but in the one before to make sure that we identify some classes of error.
And they also worked and spent a lot of time on the explicit wallback.
So that means if you didn't work, you have as a user.
Or as a package of the capability to roll back to the previous version.
And they also think that the rest is a future of Linux.
Linux has a whole distribution and also the kernel and various pieces of the stack.
And I have to do some product placement.
It's not the first major software we've done in the rest in Ubuntu.
The first one is Firefox years ago.
So I have to talk about Firefox in my slide.
So I guess everybody knows about that one.
So it's KCD.
Yeah.
I love that one.
But yeah, someone is wrong and didn't tell it.
I have a question for you who reads in the room I can use.
Yeah, almost everybody.
Cool.
Who reads phonics?
Who reads a form on phonics?
Only a few.
You're crazy.
You should not do that for your health.
It's not healthy.
Who reads Reddit.
Almost everybody.
Cool.
And who cried reading some of those comments?
Yeah, everybody.
Well, yeah, in mini situation, I'm like, especially with my works.
Sometimes people write stuff about Maria.
I'm like, oh, it's exactly what happened.
It's exactly the way things are going.
And this is the same for that project.
So what I'm going to show you now, it's by the example of people
for links or projects or things to be seen on the internet.
And trying to pass what they wrote and trying to explain what they wrote
at the time it's half.
But I also explain what else I've streamed.
We have been doing to prevent those things from happening.
So it is one of the first one.
So the worst idea I've seen in a while, people will
lie on the behavior of the new cow.
It is going to break a lot of stuff.
You will not dare yet.
So you have the source.
If you like following people, I will share the slide.
And you can click on that link and discuss with the people.
For eight months ago.
So what that person meant is in the cow materials.
We haven't documented the behavior.
I will come back to that.
We have a lot of source.
When I say we are most contributing to the upstream project.
So sometimes I'm going to confuse things.
We ignore and sometimes rest.
For me, the same.
We are all trying to do the same thing.
It's very friendly.
And we have a lot of scripts that depend on those systems.
And that person, when they wrote that,
or you are going to break stuff.
Yeah, we did.
We bought stuff.
For sure.
And we knew that.
When we started that project,
we knew that we were going to break some of the things in the bunch.
So one of the first things that we bought was the DD,
some weird usage with MD5.
That one we cut it before the release.
The second one was a back in date where
date dash R was not doing what it was supposed to do.
And we broke the unintended software upgrade.
We know the stuff that you can deploy on the deviant and
Ubuntu to automatically upgrade your system.
In the background, we are tunering.
You can challenge that statement.
That if it is more to do that or not.
This is one of the things that we bought.
That's far as I know that the only things that we bought for real in production.
But before that, as a French, I started with a negative.
So now I'm going to the positive.
We did a lot of things to prevent that from happening.
So yesterday we were at 75% of the new test suite passing in our implementation.
So long sentence or I will pass it.
But basically it means that we build our tool chain.
And we run the upstream new test suite against our words.
And we have only 5% of the tests that are not passing.
Some of them, for example, are in date.
So I learned last week that in Ethiopia,
there are different calendars and we do.
And in Ireland also, so it is a kind of thing that we are not supporting yet.
But because we are relying on the ecosystem of first,
with ICU, we can implement that easily.
It's not going to be hard.
As I said earlier, we are also not fully compliant with a PR command.
But nobody uses it so that's fine.
Except if you were working on the Unix in 72, maybe use it, but not anymore.
And we have an amazing code coverage.
So in text, I think everybody knows that if you are above 80% of code coverage,
you are usually doing a good job.
We do differential phases.
So that means that we generate some commands.
So for example, for sort, we send plenty of stupid arguments.
We're leading valid.
We send it to the new implementation, to the best implementation.
And we compare the STDR, the STDR, and the exit code.
And we do a DIF, if it is STDR, the STDR, the STDR,
the STDR, the exit code are very important.
So we verify those things.
We have also huge community.
I will share some numbers.
So we get a lot of bugs, too many bugs.
But if you don't have bugs, that probably means that we don't have users.
So I'm happy to have bugs.
And we work a lot with the Ubuntu folks.
So we build the Ubuntu archive several times with our implementation.
And in Debian and Ubuntu, we have a lot of post-picked
that runs that rely on the new tools.
So that helps you to cover a lot of things.
And not but not least, we see a lot of bug report by users,
also after we shift.
So another one.
So it may be a bad publicity for those who want to rewrite
as much as possible in the rest.
Yeah, fair.
And what I like in the sentence is that we were trained
to follow the hype of the rest.
So basically, what the person who wrote is,
we are trying to be fancy modern.
And we want to show off someone say that I'm doing that
for my resume, probably not.
But it was fun still to read that.
And obviously, the person said that we're writing
does it make it better.
Yeah, we all know that.
But I was doing it for fun, right?
So I do what I want with my free time.
And so Annubuntu was fine to be trendy.
And again, if you like to see your problems in the wrong room.
But I'm used to be diverse that you should
rewrite more things in versions of future
for stability, but also for ownership of the young generation
of the current.
So we are not chasing hype.
We use rest for concrete reasons.
So I'm not going to do a marketing speech for rest here.
But memory safety performances.
And I think one of the key things that people don't realize.
And I saw a lot of trouble about the one is that doing rest
when you write first, the code is very easily portable
to another platform.
So when people disagree with me, I like to say
think about a sea library.
Think about LibExML and try to write programs that
is going to use LibExML on max Linux and Android and Windows.
And then you start crying and you know that you're going to waste
one day of your life just making the build system correct
and build it.
With rest, you know that you do cargo in it, cargo out,
and you have your XML parser and it is going to run and build
on those platform.
And you are not going to have an issue.
In alpha and I work and do it easily.
Code code can do it in 12 seconds.
So it's super easy to do that.
So it's one of the very great things with that.
Of course, the control argument is that
you need rest to work.
So that means that you need LLVM to support that platform.
Which is a different story that I'm not going to go into.
But we have proper support in the LLN and Ubuntu for that.
So this is one of my favorite.
Absolutely.
Fact this.
I hope coroutile will be still available for saying people
along to do.
Yeah.
So it's for an ex.
Right.
So that is an emotional reaction.
And I do understand.
People don't want to break it.
Yeah, fact this.
So it's a first replacement.
So that person thing that is they're not going to be able to do a rollback.
So as I was saying, the folks that can only call their smart.
And they're doing.
So they write from the start, they have the way to rollback.
And so you can completely switch from the rest to the no implementation.
But also you can what they have done is that they realize that some of the
common.
We have to risky to switch right now.
So for example, see a challenge when you use a no Ubuntu today.
The comments table is going to point to the no implementation because
and just to be safe, we decided to leave the new one.
So, we, so that this last week is T5, everyone.
T1, number four.
Yeah, that one is, I don't know if it is a real comment.
Basically, that person called us the techno-fascist to steal Linux from us.
So, that one is really a one of five of it.
I don't know if that person was joking or not.
But it's really, we in the room, if we do it,
we have techno-fascist and we are trying to replace the old guard and so on.
So, the blog post is very long and it's very funny.
I wish that person was joking, otherwise they should see someone.
So, that person could link to also how it will work in the co-retures,
but it also the one in the GNU kernel, which are not related.
I haven't sent any email to the new storehold about that.
I don't think he cares.
But it's, there is no controversy.
We did not coordinate it.
We are not trying to replace all the GNU tools or the GNU project by, by an email
team implementation.
It's really individual project and individual choices.
Canonical is not trying to move up into our property platform.
It would be impossible even if they wanted to.
We said, don't want to do.
And I'm not involved in the internal politics.
And we're already doing way too much politics.
So, 12 number 5, that's one is what?
One of my favorite.
When you have people doing meme about your project,
I think you have an amazing line in your resume.
There is another one that I didn't share with them.
And great time to work.
Someone did that one.
I have not because I'm sick of things.
That orange face.
I'm not going to share it.
But some people did some meme about the project.
So, that person was pulling us about two bugs.
So, first one was a sort.
It was taking way too long if you had the line of two million characters.
So, do you have that in your life?
Probably not.
And the other one is a checksum.
Was 17 times slower in our implementation than the new one.
So, yeah, we have bugs.
For sure.
So, the 17 slower is because we took the approach of first.
You try to get compatibility.
And then you have the nice performances.
You don't try to first get the compatibility.
You don't try to get performances.
If you are not compatible, you do that the other way around.
And because we have one on that command,
Testing also combination is very hard.
So, we fixed it in a week.
The long line bug we fixed in the months.
And many bugs, performances, compatibility.
We fixed them in a few days.
So, what did I learn?
And what did you learn during that project?
So, rest is not to save our bullet.
If you are saying that rest is going to fix all the issues in the world.
You're probably wrong.
But it's still much better than CNC++.
But it's not a silver bullet.
You still have logic bugs.
I also learned that coralityals can be very weird.
To the points that upstream,
they may after our works, they change some of the behavior in sub-new implementation.
So, we contributed a lot.
A stream has been contributing to our project.
Two of the core maintainers have been answering to bug in our bug factor.
And we, I think, in the last release,
I'm committed number four or five.
In the blue implementation, one of the contributors, the rest project,
I think, is number three.
So, we contribute a lot to upstream, especially in the test suite.
So, the bullet strategy.
And that's why I focus at presentation on human aspect.
And not technical.
That's why I didn't share any CLI today.
Even if I love it.
It's because I came all about the human aspect of that project.
Because the bullet strategy was really key here,
and coordination, and working with smart people.
So, that slide is, I'm proud of that slide.
In the meantime, I'm also scared.
Because if you see the evolution of the number of PR on the project.
So, in 2025, we had 2,054 pull requests on that project.
That will present 4,000 commits.
So, if you work on the project, that scale, you are scared.
So, I'm afraid of burnout for now, I'm doing well.
I am lucky to have some people helping.
One of those guys in the room, other helping me with pull request.
But it's really a creative volume.
In December, we had more than 200 PR, just in December.
So, imagine, we have to save all commits.
So, when you start doing that, doing your weekend, well, not the weekend.
But doing lockdown in COVID, and you start to project by your own.
You don't have anyone to review your PR, and you have to review your own PR.
So, you don't have your stuff.
And now, we have, it's a huge success.
And last year, we had the 206 contributor.
So, it's an amazing way to run the rest.
If you are in the room, and you don't move the rest,
I'm not selling my project.
But if you want to learn, it's very easy to start.
Because you have the target.
So, you know what you are supposed to do.
You know that the new implementation is a reference.
We still have a lot of compatibility issues.
If you like playing with performances, you can do it also.
There are many, many things that we can do.
So, growing user-based, we have people also who came,
and created some introduced support for the platform.
So, we are supporting volunteers, they are 3DSD,
also major operating systems, so Linux, Mac, Windows,
Android, IQOS, we have plenty plenty of support.
And I said earlier, we contribute a lot with the new projects.
It's very friendly.
So, we are really trying to improve the state.
It's a state of the art.
Many these two are going to stick to the new project for years,
and maybe decades.
And some of the project are going to move to our worse prediction.
So, next, we want to reach one of the percent continuity.
We are pretty close.
Like I work, I like to say, you know, the parallel rules.
So, doing 80 percent of the work,
takes 20 percent of the time, and then the last 20 percent of the work,
takes 80 percent of the time.
It's not true here.
We have a lot of easy things that we need to, we can fix.
And next, after we do the next release of Canonical,
of Ubuntu, I'm going to take a break.
But then we want to work on the other program.
We have some people who already contributed to set.
So, we have a very good support of set in the rest.
We return in the rest.
We have dividers, and some people also start it,
contributing to product, PIS, and Utilianics, etc.
So, if you want to learn, and if you want to win,
win runs a wheel.
That can be a place for you to do it.
Some people, which have to listen, I want to win a playman bash.
Like sure.
So, that we know the name of the project, and we can work together.
And it's going to be fun.
Final takeaway.
So, we shipped in April.
Not sorry, it was in October, typo in the fun.
We shipped in the latest Ubuntu, and we are working with them on the 264,
mixed up the number in a few weeks.
So, we still have a few bugs that we want to fix before the release.
And so, the toll, as you saw, they were in their fear.
And even in their way, they expressed themselves.
They were not wrong about risk.
We had to identify them.
Whatever one was about processes and mitigation,
that we are not that stupid, and we know how to do those kind of changes.
And you can mitigate the risk when you are doing such big migration.
So, yeah, it was been easy, but we were hitting 30 years of expectation is not.
So, if you have time for question, I think we have a few minutes.
Thank you.