6 ms·

> keep your README succinct so why isn't yours.... node community has horrible documentation in general, at least in my experience of some shitty npm packages

> keep your README succinct so why isn't yours.... node community has horrible documentation in general, at least in my experience of some shitty npm packages i was cursed to deal with. giving non executable code samples to start.

akpa1 4y ago
> so why isn't yours.... Because this isn't a software project with a README, this is a piece of writing about READMEs that happens to be in a README.md file, likely because that's what GitHub displays by default.
- AndrewUnmuted 4y ago
  - burnished 4y ago
    It's a means of widely distributing text files that can be commented on, forked, improved, merged, and presents a history. Your alternative is hosting a blog and losing all of those features and free hosting. I do not understand how you can hold your opinion, excepting perhaps an unexamined assumption that all repositories must be exclusively for serious coding projects. Which would be understandable but, I think, in error.
- forgetfulness 4y ago
  It would serve the purpose better if it were structured closer to its own ideal of a README than a quaint millenial blog post from the 2010s
  - 5350-uiop-1130 4y ago
    the front end community is full of 20 somethings who are rediscovering the wheel every other month.
  - spartanatreyu 4y ago
    The post gives plenty of examples of the README files it's describing.
deleted 4y ago
[deleted]