From: Paul Eggert <eggert@cs.ucla.edu>
To: rms@gnu.org
Cc: eliz@gnu.org, phillip.lord@russet.org.uk, emacs-devel@gnu.org
Subject: Re: Windows emacs-25.1 i686 vs x86_64?
Date: Mon, 7 Nov 2016 08:34:48 -0800 [thread overview]
Message-ID: <eb388f04-8776-7c90-8658-3dcef23871a1@cs.ucla.edu> (raw)
In-Reply-To: <E1c3l8t-0007ih-Og@fencepost.gnu.org>
On 11/07/2016 06:43 AM, Richard Stallman wrote:
> even a few years ago
> people were still installing unauthorized copies of Windows 98 on PCs,
> because Microsoft made it harder to install subsequent Windows
> versions.
That was true fifteen years ago, but unauthorized versions of
more-recent MS-Windows systems have been widely available for ages and
they are the ones invariably installed nowadays. Last year, for example,
Microsoft announced[1] that it would give free Windows 10 licenses to
users running unauthorized copies of Windows 7 or 8.1 because
unauthorized versions were so popular (they reportedly had most of the
Chinese market). StatCounter reports that in China, where unauthorized
use is common, Windows XP had over 90% of desktop use by 2008 (with the
remainder mostly being later versions of Windows), and that nowadays
Windows 7 and Windows 10 are both more popular than XP, with the 9x line
being too small to count separately during this period.
So in practice Windows 9x is dead, and covering Windows 9x prominently
in Emacs documentation wastes users' time and makes us look technically
dated.
1. Hachman M. Microsoft offers amnesty of sorts to pirates of older
Windows software. PCWorld 2015-10-29.
http://www.pcworld.com/article/2999443/windows/microsoft-offers-amnesty-of-sorts-to-pirates-of-older-windows-software.html
next prev parent reply other threads:[~2016-11-07 16:34 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
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 [this message]
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=eb388f04-8776-7c90-8658-3dcef23871a1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
--cc=rms@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.
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.