Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Not always about scratching an itch
- Date: Wed, 04 Dec 2013 08:49:13 +0900
- From: Darren Cook <darren@example.com>
- Subject: Re: [tlug] Not always about scratching an itch
- References: <529BD5FF.7080305@dcook.org> <87li023ry8.fsf@uwakimon.sk.tsukuba.ac.jp>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5
> > 2. The examples on the project website cover just about every possible > > use case, allowing you to quickly confirm it will work in each device > > you have to support. Contrast this to more complex open source libraries > > where evaluating if something does what you need can take longer than > > the rest of the coding on the project. > > I don't understand why this comparison is interesting. Interesting for the observation you gave: open source projects that focus on one thing, the narrower the better, have a higher chance of being successful. Those that try to implement more general solutions tend to fail, and because success becomes more tied to the management of the development process than the skills of the lead developer. Unfortunately the world needs those bigger open source projects too. (GUIs are the example that come to mind first.) Darren
- Follow-Ups:
- Re: [tlug] Not always about scratching an itch
- From: Stephen J. Turnbull
- References:
- [tlug] Not always about scratching an itch
- From: Darren Cook
- [tlug] Not always about scratching an itch
- From: Stephen J. Turnbull
Home | Main Index | Thread Index
- Prev by Date: [tlug] Not always about scratching an itch
- Next by Date: Re: [tlug] Not always about scratching an itch
- Previous by thread: [tlug] Not always about scratching an itch
- Next by thread: Re: [tlug] Not always about scratching an itch
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links