I like the NIP style for describing NIPs. We shouldn't lose that. A group of people need to reach a consensus on a protocol spec, there needs to be a repository where the spec with consensus lives. guides suck and get outdated.
Discussion
But these things you are saying are the same things that serve as the basis for my article and against which I argue. Now you're just restating then as an answer to the article?
Well, except for "guides suck and get outdated", to which I reply that NIPs suck and get outdated too, in fact they may not get outdated because they're horribly incomplete from the start in most cases.
It feels like you didn't read the article. The point is assigning kinds is more functional than a schema that doesn't (in most cases) define what relays or UI/UX will be needed. The consensus is adoption. Everyone doesn't have to agree, they just use it if they like it. Guides should be written with that in mind and be written in the most program and tool agnostic way.