From: "alírio eyng" <alirioeyng@gmail.com>
Cc: guix-devel@gnu.org, gnu-linux-libre@nongnu.org
Subject: Re: MAME emulator is giving incentive to use non-free software
Date: Sun, 3 Apr 2016 14:20:22 +0000 [thread overview]
Message-ID: <CALkz57F9tdCBg+bAGCsksT+ZenmzxxTYFFZ95pc3RyguvpH+Hw@mail.gmail.com> (raw)
In-Reply-To: <CALkz57F-T1E+veEONCwkW9uRNgTD49HNpC1NUQDx2kBkm51vMw@mail.gmail.com>
i think i got the root of the controversy:
some people started to think of emulators as hardware (replacements)
hardware is useful to develop to
some people started to think of emulators as obsolete apis
obsolete apis are not useful to develop to
i still see emulators (like ndiswrapper) as obsolete apis; without
free applications that can't run natively they are useless and should
be removed so the user doesn't run nonfree software by mistake
unless they emulate current hardware (like qemu), in this case they
are useful in themselves (don't need a free application that can't run
natively), just being hardware replacements helping development
wine is a exception to introduce free software in nonfree platforms
the compromise is define _current hardware_
"MAME now documents a wide variety of (mostly vintage) computers"[1]
_vintage_ seems undoubtly out _current hardware_
i also noticed i was conflating technical details i shouldn't
my approach was to make an opt-out whitelist of free uses (mostly
games) for packages with a nonfree community (mostly emulators like
mame or wine) implemented with the package manager/filesystem
[1]http://mamedev.org/
next prev parent reply other threads:[~2016-04-03 14:20 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 16:31 MAME emulator is giving incentive to use non-free software alírio eyng
2016-03-30 22:30 ` Isaac David
2016-04-02 3:17 ` Denis 'GNUtoo' Carikli
2016-03-31 22:50 ` alírio eyng
2016-04-01 6:23 ` Ricardo Wurmus
2016-04-01 12:15 ` alírio eyng
2016-04-01 20:03 ` alírio eyng
2016-04-02 2:19 ` Denis 'GNUtoo' Carikli
2016-04-02 8:48 ` [GNU-linux-libre] " alírio eyng
2016-04-03 14:20 ` alírio eyng [this message]
2016-04-03 18:36 ` alírio eyng
2016-04-03 19:39 ` Felipe Sanches
2016-04-03 21:02 ` alírio eyng
2016-04-03 21:22 ` Felipe Sanches
2016-04-04 3:26 ` alírio eyng
2016-04-04 11:19 ` Felipe Sanches
2016-04-04 22:23 ` alírio eyng
2016-04-04 22:47 ` [GNU-linux-libre] " Felipe Sanches
2016-04-04 22:58 ` Felipe Sanches
2016-04-04 22:59 ` Felipe Sanches
2016-04-05 2:29 ` alírio eyng
2016-04-09 9:00 ` Denis 'GNUtoo' Carikli
2016-04-09 19:43 ` alírio eyng
2016-04-27 0:31 ` [GNU-linux-libre] " alírio eyng
2016-04-05 15:59 ` Denis 'GNUtoo' Carikli
2016-04-06 11:02 ` alírio eyng
-- strict thread matches above, loose matches on Subject: below --
2016-03-30 4:10 IngeGNUe
2016-03-30 16:11 ` Mark H Weaver
2016-03-30 21:26 ` IngeGNUe
2016-03-29 14:01 Jean Louis
2016-03-29 14:46 ` Nils Gillmann
2016-03-28 21:55 Jean Louis
2016-03-29 0:26 ` Jookia
2016-03-29 4:42 ` Jean Louis
2016-03-29 6:27 ` Jookia
2016-03-29 7:30 ` Jean Louis
2016-03-29 8:25 ` Jookia
2016-03-29 11:35 ` rain1
2016-03-29 12:00 ` Jean Louis
2016-03-29 12:48 ` Nils Gillmann
2016-03-29 14:23 ` Mathieu Lirzin
2016-03-29 14:52 ` Jean Louis
2016-03-29 16:15 ` Ludovic Courtès
2016-03-29 17:29 ` Jean Louis
2016-03-29 17:47 ` Jean Louis
2016-03-29 12:41 ` Nils Gillmann
2016-03-29 1:44 ` Mark H Weaver
2016-03-29 13:03 ` Ludovic Courtès
2016-03-29 17:30 ` Christopher Allan Webber
2016-03-29 17:32 ` Thompson, David
2016-03-29 17:37 ` Eric Bavier
2016-03-30 20:25 ` Ludovic Courtès
2016-03-29 8:58 ` Taylan Ulrich Bayırlı/Kammer
2016-03-29 10:12 ` Jean Louis
2016-03-29 13:14 ` Ludovic Courtès
2016-03-29 13:51 ` Jean Louis
2016-03-29 16:09 ` Ludovic Courtès
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=CALkz57F9tdCBg+bAGCsksT+ZenmzxxTYFFZ95pc3RyguvpH+Hw@mail.gmail.com \
--to=alirioeyng@gmail.com \
--cc=gnu-linux-libre@nongnu.org \
--cc=guix-devel@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/guix.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.