My understanding is that tailwind is a framework consisting of utility classes corresponding to css fragments. If its missing a fragment you want, then you can

My understanding is that tailwind is a framework consisting of utility classes corresponding to css fragments. If its missing a fragment you want, then you can add that fragment - either as a custom class, or as a tailwind "managed" class. Managed classes basically mean a bit of magic (compilation) around sizing, etc is applied. The compiler then strips out all the stuff that doesnt get used. The "leakiness" that the author mentions seems to be focused around elements "injecting" styles into their child components. They then go on to suggest alternative underlying css that may be better. Maybe this should instead be an issue/PR raised against the respective managed classes rather than a criticism of the framework as a whole?