From: Nala Ginrut <nalaginrut@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Thien-Thi Nguyen <ttn@gnu.org>,
"guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Popularity (was Re: SLAYER announcement ...)
Date: Mon, 06 May 2013 11:25:01 +0800 [thread overview]
Message-ID: <1367810701.3076.5.camel@Renee-desktop.suse> (raw)
In-Reply-To: <1367782954.57806.YahooMailNeo@web120405.mail.ne1.yahoo.com>
On Sun, 2013-05-05 at 12:42 -0700, Mike Gran wrote:
> > From: Thien-Thi Nguyen <ttn@gnu.org>
>
> > As Guile-SDL maintainer, i wonder what i can do to attract the same
> > audience, whether or not it is worth expending the energy to do so, in
> > what ways have i failed to encourage organic additive (as opposed to
> > parallel) hacking, and how wonderful/terrible it is for GNU to be so
> > loosely coupled.
>
> Working on a library or framework is always a thankless task, since
> so few programmers want to use the unproven. Gtk would not be where
> it is if it weren't for the co-development of Gimp, an end-user
> program.
>
> Getting someone to try an end-user program is easier than getting
> a programmer to try out a library. But that is difficult as well.
> Since every essential end-user program has been written -- all new
> work just re-mixes the old ideas in either shinier or deeper ways --
> few people are in "need" of new software.
>
> But there is always space for new diversions: there still seems to
> be a market for something short, easy to run, and entertaining.
> The Flash or HTML5 games model, essentially.
>
> One might consider writing an end-user program first,
> and then note how it is built upon libraries that can
> easily be reused.
>
> (And speaking of libraries that will never be used... guile-ncurses
> v1.4 dropped last week. That'll never have any users because the
> intersection in that Venn diagram is too small, consisting mostly of
> me. So, I write it for myself. Maybe I should follow my own
> advice above.)
>
No Mike, I use guile-ncurses for a little thing to peek stock
market. ;-P
And TTN, your work is nice.
We just don't have a web community yet, so many folks and projects are
unrevealed.
> -Mike
>
next prev parent reply other threads:[~2013-05-06 3:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 21:54 SLAYER announcement and help request for preparing a GNU package Panicz Maciej Godek
2013-05-05 5:15 ` John Darrington
2013-05-05 6:55 ` Stjepan Horvat
2013-05-05 6:59 ` Panicz Maciej Godek
2013-05-05 18:48 ` Thien-Thi Nguyen
2013-05-05 19:42 ` Popularity (was Re: SLAYER announcement ...) Mike Gran
2013-05-05 20:04 ` Popularity Frank Terbeck
2013-05-05 22:12 ` Popularity (was Re: SLAYER announcement ...) Chris Vine
2013-05-06 3:25 ` Nala Ginrut [this message]
2013-05-07 12:20 ` Ludovic Courtès
2013-05-05 21:37 ` SLAYER announcement and help request for preparing a GNU package Panicz Maciej Godek
2013-05-06 8:06 ` Javier Sancho
2013-05-06 19:36 ` Panicz Maciej Godek
2013-05-06 21:25 ` Thien-Thi Nguyen
2013-05-07 22:50 ` Panicz Maciej Godek
2013-05-08 9:34 ` Thien-Thi Nguyen
2013-05-08 12:51 ` Panicz Maciej Godek
2013-05-08 13:37 ` Mark H Weaver
2013-05-08 15:15 ` Mike Gran
2013-05-08 21:44 ` Panicz Maciej Godek
2013-05-09 6:50 ` Thien-Thi Nguyen
2013-05-08 21:56 ` Ludovic Courtès
2013-05-07 7:23 ` Javier Sancho
2013-05-07 22:00 ` Panicz Maciej Godek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1367810701.3076.5.camel@Renee-desktop.suse \
--to=nalaginrut@gmail.com \
--cc=guile-user@gnu.org \
--cc=spk121@yahoo.com \
--cc=ttn@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).