> programmers should try and write their software in a way that makes reasonable use of the resources of the computer.
As programmers, I think we should build tools to help us with that. This kind of article will appeal to people already sensitive to performance, just like talking about software craftsmanship will appeal to people already proud of their job. But if we want to change the industry for the better, we have to enforce that with tools.
Since Rust is used here, we could imagine something like clippy (a linter) but for performance. You could have lots of options, with a few defaults performance levels. For example, at performance level 0 (minimal performance), lines() is fine. At level 1, it could become a warning. At level 2, an error.
The problem I see is that while lines() is easy to fix, the part about Unicode would be harder to do, and that was where most of the performance improvements were found. Maybe that can be fixed at the library level?