Hacker News Reader

Comment by automatic6131 | Hacker News Reader

The absolute state of github projects.

This project should be exactly 1 (one) file. The readme.md.

LICENSE - There is a license? Why? Someone might steal the text for their own blog post? So what? The license won't stop them.

package.json - to install dozens of packages for... eslint. Just install globally. It's just markdown and code examples. Yarn.lock - ah yeah let's have this SINGLE, NON EXECUTABLE TEXT FILE be opinionated on the javascript package manager I use. Good stuff We have a .gitignore, just to hide the files eslint needs to execute. wow. FUNDING folder - wow we have an ecosystem of stating the funding methods?

This should have never been a github repo. This is a blog post. It's a single, self contained post.

I hate this crap. We have 9 files just to help 1 exist. It's aesthetically offensive.

View on HN

Wow, where should I start

> LICENSE - There is a license? Why? Someone might steal the text for their own blog post? So what? The license won't stop them.

But it’s still good that author underlined that he don’t want it to be copied. What’s wrong with that?

> package.json - to install dozens of packages for... eslint. Just install globally.

Then other contributors won’t know what version he used, what config he had, he won’t be able to easily recreate it on different computer, etc…

> Yarn.lock - ah yeah let's have this SINGLE, NON EXECUTABLE TEXT FILE be opinionated on the javascript package manager I use.

That’s author choice. Any good argument against it or you will just criticize for the sake of it?

> This should have never been a github repo. This is a blog post. It's a single, self contained post.

It’s a blog post with 270 different revisions, 80 contributors and a bunch of different languages. Show me how to easily do that with a blog post.

> I hate this crap. We have 9 files just to help 1 exist. It's aesthetically offensive

Why number of files is offensive to you? We have a couple tools good at what they do to keep things consistent and organized. Better to have these tools to keep standards than not.

The document appears to have 80 contributors, that's hard to do with a blog post. It could have been a wiki page. But then I'm not sure if hosting a single repo on Github is harder than hosting a wiki. And of course Github provides superior platform for collaboration compared to a wiki.

I think it's cool that it's a repo. Now other people can submit pull requests and improve it. As for the files, bah whatever. Go find a squirrel to bark at.

Why do you care? Just link directly to the rendered markdown.

Reply on news.ycombinator.com