> This is, ironically enough, a microcosm of the post author’s complaint: people are replying to their patches without having done the due diligence of gaining

> This is, ironically enough, a microcosm of the post author’s complaint: people are replying to their patches without having done the due diligence of gaining context in their own first, and are offloading that burden of gaining context onto the patch author instead — which is slowly burning them out Eh, I get it. Understanding anything takes effort, and each one of us has a limited amount of mental energy per day. Nobody likes wasting it for what they feel is responsibility of another. I wouldn't criticize the author for what happened in the kernel discussion - I don't have enough skill or experience to understand why or how is anyone right or wrong. What I do have a problem with, is posting an article like this on HN, then shutting every comment down with "read these 15000 lines, peasant, before you even dare to speak". Most people on HN are not kernel hackers, so why the (if I may be blunt - pretentious) gatekeeping? There must be some better way of explaining why someone's comment is wrong than "here, read this large text, figure it out yourself and don't come back until you figure it out". That's just lazy and disrespectful.