From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Pascal J. Bourguignon" Newsgroups: gmane.emacs.help Subject: Re: Issues with emacs Date: Sun, 24 Jun 2012 03:24:15 +0200 Organization: Informatimago Message-ID: <8762ahcxj4.fsf@kuiper.lan.informatimago.com> References: <87bokbb4zw.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1340501117 19613 80.91.229.3 (24 Jun 2012 01:25:17 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 24 Jun 2012 01:25:17 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Jun 24 03:25:13 2012 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SibZg-0003VR-PD for geh-help-gnu-emacs@m.gmane.org; Sun, 24 Jun 2012 03:25:12 +0200 Original-Received: from localhost ([::1]:42289 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SibZg-0001qb-LX for geh-help-gnu-emacs@m.gmane.org; Sat, 23 Jun 2012 21:25:12 -0400 Original-Path: usenet.stanford.edu!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 57 Original-X-Trace: individual.net PYqL6y4h+FI2kvawBwdKbw8orjxZluWXC8NuMfY5VTOHxA0FB0CGyRqgoWNlJmPeJi Cancel-Lock: sha1:N2RlNmVkNTA1NDc4ZGYwOWI1MGQ3NDMwZDBkYjcwYjc3ZjVmNjI0Nw== sha1:GEptHCjTvDESctMT7sU+ZlNrb34= Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwAQMAAABtzGvEAAAABlBMVEUAAAD///+l2Z/dAAAA oElEQVR4nK3OsRHCMAwF0O8YQufUNIQRGIAja9CxSA55AxZgFO4coMgYrEDDQZWPIlNAjwq9 033pbOBPtbXuB6PKNBn5gZkhGa86Z4x2wE67O+06WxGD/HCOGR0deY3f9Ijwwt7rNGNf6Oac l/GuZTF1wFGKiYYHKSFAkjIo1b6sCYS1sVmFhhhahKQssRjRT90ITWUk6vvK3RsPGs+M1RuR mV+hO/VvFAAAAABJRU5ErkJggg== X-Accept-Language: fr, es, en User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Original-Xref: usenet.stanford.edu gnu.emacs.help:193010 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:85405 Archived-At: Dan Espen writes: > Tom writes: > >> Bastien gnu.org> writes: >> >>> >>> The good news is that, whether Emacs users are a dying breed >>> or not, the only remedy to this hypothetical issue is to have >>> more Emacs developers. >>> >> >> But how to have more developers. I see 3 possibilites: >> >> 1. Motivate more users to be volunteer developers? Any idea how >> to do that? >> >> 2. Attracting more users. Volunteer developers are some small >> percent of the active user base, so if Emacs can be mode more >> attractive to users then the bigger user base will bring more >> volunteer developers too. The problem is in order to be more >> attractive Emacs needs new features which other editors/IDEs have >> and which make users to choose those editors/IDEs instead of >> Emacs, and to implement those more competitive features Emacs >> needs more developers. >> >> 3. Crowdfunding. If we don't have enough volunteer developers >> then we need to motivate developers with something else. For >> example, paying for their work. For this model to work there >> should be some public exposure of this idea, so potential >> developers know they can potentially make a living while >> contributing to Emacs. This kind of public exposure could be done >> by RMS who could mention this development model in every >> interview he gives. He has the voice which can reach lots of >> ears, including potential developer ears. It'd be nice to have some reliable statistics, such as: - absolute number of users of emacs. - % of non-programmer users of emacs. - histogram of programming languages (or in general modes) edited in emacs. > 4. Have a whole bunch of missing functionality. :-) But it looks like there could be some improvements indeed. -- __Pascal Bourguignon__ http://www.informatimago.com/ A bad day in () is better than a good day in {}.