From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Kernel ricing
Date: Fri, 25 Oct 2013 08:39:19 +0200 [thread overview]
Message-ID: <526A1217.1070603@gmail.com> (raw)
In-Reply-To: <52695AA5.7000700@libertytrek.org>
On 24/10/2013 19:36, Tanstaafl wrote:
> On 2013-10-24 1:03 PM, Bruce Hill <daddy@happypenguincomputers.com> wrote:
>> I'm not positive of it's architecture, but for 20 months I had a Samsung
>> Galaxy S running Android. This was by far the biggest POS I ever
>> owned. From
>> the first week it spontaneously rebooted, hung, and the performance was
>> horrible when it did run.
>>
>> I've since switched to an iPhone 4S, now running iOS 7.0.2. It Just
>> Works (TM)
>
> Oh, please, spare me the ridiculous apple fanboi crap-crud.
>
> Just because you got a phone that was bad, and didn't bother to get it
> replaced, doesn't make all Galaxy S4 phones as bad as yours.
>
> I'll tell you this, my Nexus 4 is absolutely rock-solid, and screaming
> fast, but that doesn't mean iPhones suck.
>
Phones are like cars in that almost no-one makes a bad one anymore.
Pick a smart phone, any smart phone, and I can almost assure you that in
this vast cavern of a room where I work I will find 3 people within an
hour who have or had that phone. The last smart phone model that had a
serious defect that applied across the range was the iPhone that had
antenna problems.
Since then everyone's shit just works for the most part like it was
designed to. Even the Windows 8 thingy from Nokia. It does what it says
on the box.
Yes, software bugs exist such as Apple's maps but that's not phone
design, that's bad data fed into a db that an app uses
These days the most relible way to pick a phone that will work for you
is the one that a) runs the software you like if you care about such
things and b) feels nice in your hand and fits in your pocket
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2013-10-25 6:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 8:58 [gentoo-user] Kernel ricing Adam Carter
2013-10-24 9:06 ` Alan McKinnon
2013-10-24 10:58 ` Adam Carter
2013-10-24 11:39 ` Alan McKinnon
2013-10-24 15:26 ` [gentoo-user] " James
2013-10-24 15:33 ` Alan McKinnon
2013-10-24 16:21 ` James
2013-10-24 17:03 ` Bruce Hill
2013-10-24 17:31 ` James
2013-10-24 17:50 ` Bruce Hill
2013-10-25 15:07 ` James
2013-10-24 17:36 ` Tanstaafl
2013-10-24 17:51 ` Bruce Hill
2013-10-24 17:55 ` Tanstaafl
2013-10-24 17:54 ` James
2013-10-25 6:39 ` Alan McKinnon [this message]
2013-10-30 7:22 ` Grant
2013-10-25 0:15 ` [gentoo-user] " Walter Dnes
2013-10-24 11:48 ` the
2013-10-24 16:22 ` [gentoo-user] " James
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=526A1217.1070603@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@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