From: Daniel Colascione <dancol@dancol.org>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: phillip.lord@russet.org.uk, emacs-devel@gnu.org
Subject: Re: Windows emacs-25.1 i686 vs x86_64?
Date: Sun, 6 Nov 2016 13:57:36 -0800 [thread overview]
Message-ID: <f42f1e8a-662c-5036-fba2-4ce15d0f2338@dancol.org> (raw)
In-Reply-To: <05ba947a-970a-178c-8036-bcdf84485384@cs.ucla.edu>
On 11/06/2016 01:54 PM, Paul Eggert wrote:
> Eli Zaretskii wrote:
>> Windows/ME was never popular, even when it was released
>
> As I understand it, that "WinME" label is a catchall that includes the
> MS-Windows 9x line, and "0.01%" is so small that I doubt whether it is
> statistically significant. In practice then 9x line has transitioned
> from unsupported (ten years ago) to on-its-way-out (five years ago) to
> dead (now, almost everywhere), and any old decisions that assumed 9x's
> viability are now obsolete.
>
> In GNU projects, we typically stop worrying about an underlying platform
> when its original supplier stops supporting it. For example, Emacs no
> longer worries about IRIX because SGI stopped supporting IRIX in 2013.
> Although MS-Windows 9x is special partly because it was so popular long
> ago, Emacs need not support 9x indefinitely, and Emacs's documentation
> should not give Emacs users the incorrect impression that 9x is still a
> live platform.
It would be nice to have a data-based condition for dropping 9X support.
Windows 9X already well beyond the level of dead past which we stop
supporting other platforms, and it'd be nice to have a clear
understanding of when we can finally drop 9X support --- this way, we'll
know when we can drop XP support.
next prev parent reply other threads:[~2016-11-06 21:57 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 15:32 Windows emacs-25.1 i686 vs x86_64? David M. Miller
2016-11-03 15:39 ` tomas
2016-11-03 16:00 ` David M. Miller
2016-11-03 16:26 ` John Mastro
2016-11-03 16:28 ` Phillip Lord
2016-11-03 17:44 ` David M. Miller
2016-11-03 22:21 ` Phillip Lord
2016-11-03 17:58 ` Eli Zaretskii
2016-11-03 22:25 ` Phillip Lord
2016-11-04 7:19 ` Eli Zaretskii
2016-11-04 10:19 ` Phillip Lord
2016-11-05 8:16 ` Eli Zaretskii
2016-11-05 22:26 ` Phillip Lord
2016-11-06 3:43 ` Eli Zaretskii
2016-11-06 8:10 ` Paul Eggert
2016-11-06 15:48 ` Eli Zaretskii
2016-11-06 16:13 ` Óscar Fuentes
2016-11-06 16:43 ` Eli Zaretskii
2016-11-06 17:01 ` Óscar Fuentes
2016-11-06 17:24 ` Eli Zaretskii
2016-11-06 18:26 ` Óscar Fuentes
2016-11-06 18:42 ` Eli Zaretskii
2016-11-06 19:17 ` Eli Zaretskii
2016-11-06 20:15 ` Óscar Fuentes
2016-11-07 14:40 ` Richard Stallman
2016-11-07 15:16 ` Phillip Lord
2016-11-08 13:53 ` Richard Stallman
2016-11-06 16:51 ` Stefan Monnier
2016-11-06 18:50 ` John Wiegley
2016-11-07 14:42 ` Richard Stallman
2016-11-06 21:54 ` Paul Eggert
2016-11-06 21:57 ` Daniel Colascione [this message]
2016-11-07 14:43 ` Richard Stallman
2016-11-07 15:15 ` Daniel Colascione
2016-11-07 15:26 ` Phillip Lord
2016-11-08 13:53 ` Richard Stallman
2016-11-08 14:52 ` Phillip Lord
2016-11-08 15:31 ` Eli Zaretskii
2016-11-09 16:50 ` Phillip Lord
2016-11-09 17:15 ` Eli Zaretskii
2016-11-09 17:18 ` Stefan Monnier
2016-11-10 15:19 ` Phillip Lord
2016-11-09 7:00 ` martin rudalics
2016-11-15 10:26 ` Phillip Lord
2016-11-07 16:34 ` Paul Eggert
2016-11-07 18:07 ` Eli Zaretskii
2016-11-07 19:02 ` Perry E. Metzger
2016-11-07 19:29 ` Eli Zaretskii
2016-11-07 21:54 ` Phillip Lord
2016-11-07 19:39 ` Stefan Monnier
2016-11-07 20:02 ` Perry E. Metzger
2016-11-07 20:10 ` Stefan Monnier
2016-11-07 20:22 ` Perry E. Metzger
2016-11-07 20:27 ` Eli Zaretskii
2016-11-08 3:48 ` Elias Mårtenson
2016-11-08 15:32 ` Eli Zaretskii
2016-11-07 18:49 ` Perry E. Metzger
2016-11-08 13:55 ` Richard Stallman
2016-11-08 14:34 ` Perry E. Metzger
2016-11-06 21:50 ` Phillip Lord
2016-11-06 4:13 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f42f1e8a-662c-5036-fba2-4ce15d0f2338@dancol.org \
--to=dancol@dancol.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.