In isolation, they're not crazy. But much C code is bringing in library headers which contain their author's own pet choices for these, which inevitably are no

In isolation, they're not crazy. But much C code is bringing in library headers which contain their author's own pet choices for these, which inevitably are not the same and the result is extremely confusing when you have that in play as well as the stdint.h ones. The kernel contains a mixture of "pet" types like u32 and stdint ones, it's already confusing. He also does make a "crazy" choice later to call his string class "s8" which clashes with his nomenclature here.