Ummm...

@vitaut the problem wtih vibe coding is when you have to spend all the time making the code not fucking suck afterwards.

It's a bit annoying to think I'll send a series with Ass-by on it that I spent hours and hours doing that on, but some arsehole will send one using open claw that he didn't even look at... :O

@vitaut is it the fact you're dealing with IEEE whatever whatever floating point that makes lean useful or could there be uses of it that might be helpful in other realms, such as the kernel?

I suppose something strictly mathematical lends itself well to it better than usual code :)

Jula Lawall (who's great) has given a talk on formal verification in the kernel, e.g. this one at KR - https://kernel-recipes.org/en/2025/schedule/program-verification-for-the-linux-kernel-potential-costs-and-benefits-tentative/ - that seems to ultimately conclude (in my view :) that it's really not all that practical except for perhaps very specific parts of it.

But I wonder if lean changes things in any way... :)

@vitaut keys made of pasta

@vitaut *schlopped one-linear in awk

@vitaut wait what shit that's a good idea

I wrote a book on Linux Memory Management, published by @nostarch - it's a comprehensive 1300 page exploration of Linux 6.0's memory management code, depth-first, diving into the code and REALLY explaining how things work.

The idea is to avoid hand waving as much as possible and literally explore what the kernel _actually_ does.

It's full of diagrams and careful explanations of logic including a ton of stuff you just can't find anywhere else.

It's currently available in its entirety in draft form via early access when you pre-order.

It's available at https://nostarch.com/linux-memory-manager

:)

#linux #kernel #mm