7 comments

[ 3.1 ms ] story [ 25.9 ms ] thread
(comment deleted)
This seems well-reasoned and clear. The author is pissed off, but one can see why if what the article presents is accurate.

But I personally don't know either the code base or the material ("terminals") well enough to be potentially able to confirm or refute it.

It'd be great to see some refutation of this article or a defense of the original changes so we could make up our minds.

This is expected as OSS developers are, for the most part, amateurs. Nobody is paying them for their work. They're not professionals, so one shouldn't expect professional behavior. It's not even bush league. Once they graduate from high school or college and write software for a living (if they get there), their standards will improve. Of course, at that point they don't really have time to contribute to OSS anymore. So it's all n00bs, all the time.
> Nobody is paying them

> They're not professionals

> shouldn't expect professional behavior

> It's not even bush league

> they don't really have time

Dude, you're champion of excuses. Maybe it's worth to stop making them and just fix the highlighted problems?

What I don't understand is why forks don't happen more often.
Looking at the post history from that site on HN, it's amazing how the author of the post keeps finding projects with totally irrational leadership that can't accept brilliant ideas /s
That's because if I don't have any problems with a project that has rational leadership there's no point in me writing a blog post shining a light into something that doesn't exist, is there?

Have you heard of survivorship bias?