I think the important bit here is: a Linux scheduler written "during Christmas break, just for fun", is better that the current one.
it might be the developer sense of "fun", it might be rust, but it is impressive, notheless
...with certain workloads
i.e. it might be a bit better in a few specific cases, but a bit worse in a large number of more common workloads.
Not that I'm trying to take anything away from the work - getting on par with the well-tuned-over-many-years scheduler for any workloads is an impressive feat. But saying it's "better than the current one" without the caveats made by the original author is oversimplifying to the point of being misleading, I think.