public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: amd64 list, still useful?  Was: btrfs
Date: Fri, 30 May 2014 06:25:19 +0000 (UTC)	[thread overview]
Message-ID: <pan$d0023$c5612040$5d9d9f02$41927e0c@cox.net> (raw)
In-Reply-To: 20140529224405.898d1137a9a404b36c679f9a@comcast.net

Frank Peters posted on Thu, 29 May 2014 22:44:05 -0400 as excerpted:

> On Fri, 30 May 2014 02:04:39 +0000 (UTC)
> Duncan <1i5t5.duncan@cox.net> wrote:
> 
>> FWIW, I'm no-multilib as well, but I guess for a different reason.
>> 
>> I don't do proprietary [...]
>>
> It's not just proprietary software that lags behind.  I continue to
> encounter FOSS packages from time to time that are still 32-bit only.
> 
> One example, for audio enthusiasts, is the excellent AudioCutter:
> http://www.virtualworlds.de/AudioCutter/

I'm not saying 32-bit-only FLOSS isn't out there, only that by now, and 
actually from 2010 or so (to pick the turn of the decade as a convenient 
date, one could actually say by 2008 or so), it's increasingly non-
mainstream.  There's the occasional exception, but for most people, 
either their 32-bit concerns are proprietary only, or there's a more 
mainstream 64-bit alternative.

Luckily for me, my interests are mainstream enough...

> (There are many other examples but at this moment I can't recall any
> specific names so you'll just have to trust me).
> 
> However, when it comes to the PDF file format it is hard to beat the
> proprietary Foxit Reader.  With FOSS only evince comes close but evince
> lacks a lot of capability and seems to be buggy in places.

I should explicitly mention that I'm all for people making their own 
decisions regarding proprietary.  Because I know if someone had tried to 
push me before I was ready, even while I was preparing for my ultimate 
switch, the results would have been nothing but negative.  So everyone 
must move when they are ready, and if that time never comes, well...  But 
at the same time, that decision is behind me personally, and there's 
simply no way I'm going back to the days of proprietary.

As for pdf, I'm running (semantic-desktop-stripped) kde and okular, and 
have been reasonably happy with it.  Where I've seen people complain 
about PDF readability or compatibility and have checked, okular has done 
well enough for me, to the point I never saw what they were complaining 
about.

Meanwhile, even if I did find some PDF nothing I could run would handle, 
that would simply mean I'd not read that pdf, tho if it was worth it I 
could envision taking it to the library to read or to a printer to have 
them print it out or something.  But I wouldn't install anything 
proprietary on my own systems to read it.  There are too many other 
things to do in the world to worry about missing what's in one pdf, 
especially if it meant my freedom was on the line.

> AMD64 should be the standard but many projects refuse to update since
> reliance on multi-lib is so much simpler.  As a consequence we 64-bit
> purists are at a disadvantage.

True at times.  Luckily, those times aren't so frequent these days.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2014-05-30  6:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 22:13 [gentoo-amd64] Soliciting new RAID ideas Mark Knecht
2014-05-27 22:39 ` Bob Sanders
2014-05-27 22:58   ` Harry Holt
2014-05-27 23:38     ` thegeezer
2014-05-28  0:26       ` Rich Freeman
2014-05-28  3:12       ` [gentoo-amd64] btrfs Was: " Duncan
2014-05-28  7:29         ` thegeezer
2014-05-28 20:32           ` Marc Joliet
2014-05-29  6:41             ` [gentoo-amd64] " Duncan
2014-05-29 17:57               ` Marc Joliet
2014-05-29 17:59                 ` Rich Freeman
2014-05-29 18:25                   ` Mark Knecht
2014-05-29 21:05                   ` Frank Peters
2014-05-30  2:04                     ` [gentoo-amd64] amd64 list, still useful? Was: btrfs Duncan
2014-05-30  2:44                       ` Frank Peters
2014-05-30  6:25                         ` Duncan [this message]
2014-06-04 16:41                       ` Mark Knecht
2014-06-05  2:00                         ` [gentoo-amd64] " Duncan
2014-06-05 18:59                           ` Mark Knecht
2014-06-06 12:11                             ` Duncan
     [not found]                           ` <Alo71o01J1aVA4001lo9xP>
2014-06-06 17:07                             ` Duncan
2014-05-27 23:32   ` [gentoo-amd64] Soliciting new RAID ideas Mark Knecht
2014-05-27 23:51   ` Marc Joliet
2014-05-28 15:26     ` Bob Sanders
2014-05-28 15:28       ` Bob Sanders
2014-05-28 16:10       ` Rich Freeman
2014-05-28 19:20       ` Marc Joliet
2014-05-28 19:56         ` Bob Sanders
2014-05-29  7:08         ` [gentoo-amd64] " Duncan
2014-05-27 23:05 ` [gentoo-amd64] " Alex Alexander

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='pan$d0023$c5612040$5d9d9f02$41927e0c@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.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