Hacker News new | ask | show | jobs
by keyle 666 days ago
I don't know the author but it's worth keeping in mind that... Sometimes people end working on a project because

- it has no future, ran its course, proved wrong somehow

- cannot add more that others could do better

- an alternative makes more sense long term

It's true that many people end working on something because it gets too hard or they lack focus.

But in this case, seeing the breath of the projects, this is not the case.

3 comments

Absolutely, thanks for pointing that out. I really hope it didn't come across as condescending, as I didn't intend it to be - because I have the same habit. Do something until it's not exciting anymore and move on. Though unlike myself more often, he tends to actually finish what he's working on initially.

I guess I was trying to paint a short historical picture and why I'm pretty excited about it as a Solus user - its package manager is a bit long in the tooth. I think could be a really great relationship having one team/person prototype and another adopt into something more stable.

Sometimes you start a project, more and more people start to collaborate, and eventually most of the project's contributors want to move it in a direction that doesn't interest you.

At that point you can either be a spoilsport, or step away amicably.

I would add:

- it accomplished the task of teaching some technology/language/practice to the author, so that it becomes subjectively useless after that knowledge is absorbed.

Sometimes people start building a car because they need an incentive to practice making wheels.