From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: OT: advice sought on new laptop for Gentoo
Date: Mon, 06 Sep 2010 18:48:11 -0400 [thread overview]
Message-ID: <yu9bp8ajxp0.fsf@nyu.edu> (raw)
In-Reply-To: <i634kd$1c7$1@dough.gmane.org> (Grant Edwards's message of "Mon, 06 Sep 2010 16:24:45 +0000 (UTC)")
Grant Edwards <grant.b.edwards@gmail.com> writes:
> For a given height, a 16:9 display is 30% wider. I want nice tall
> display (prefereably at least 9-10") without having to increase the
> width beyond what a standard "laptop" style keyboard takes up (about
> 12-13 inches).
It is certainly true that, if the height of the display is the key
factor and hence fixed, a wider screen will add more inches (I again
assume square pixels).
However, those extra inches and resulting extra pixels are far from
useless. I believe you are selling "two up" short. When I am preparing
a course, I have the html up in one (emacs) window and the resulting web
page in another (firefox) window immediately to its right. Heck I very
much use and enjoy 3-up on my large (30" 2560x1600) monitor.
> Perhaps I'm too cynical, but IMO the "cheap" factor is why we got 16:9
> displays on laptops in the first place. A 15" 16:9 display is roughly
> 10% smaller (cheaper) than a 15" 4:3 display. But, the salesdroid can
> talk the consumer into paying more for a cheaper product: "Wow, for
> only $100 more we can move you up from a 15" regular display to a 15"
> WIDESCREEN display!
>
> $100 more and it's 1.6" shorter and has 10% less screen area!
>
> What a deal!!
You are correct that this salesperson was, perhaps out of
ignorance--perhaps malice) making a specious argument. But limiting
purchases to items for which a salesperson cannot argue speciously, is
not the best selection criterion.
allan
next prev parent reply other threads:[~2010-09-06 22:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 12:58 [gentoo-user] OT: advice sought on new laptop for Gentoo John Blinka
2010-09-05 14:02 ` Florian Philipp
2010-09-05 15:18 ` [gentoo-user] " Grant Edwards
2010-09-05 19:25 ` Alan McKinnon
2010-09-05 22:04 ` Allan Gottlieb
2010-09-06 11:08 ` Stroller
2010-09-05 23:42 ` Grant Edwards
2010-09-06 0:21 ` Al
2010-09-06 6:16 ` Alan McKinnon
2010-09-06 16:24 ` Grant Edwards
2010-09-06 22:02 ` Mick
2010-09-06 22:48 ` Allan Gottlieb [this message]
2010-09-07 2:04 ` Grant Edwards
2010-09-07 14:38 ` Allan Gottlieb
2010-09-07 16:15 ` Robert Bridge
2010-09-07 16:34 ` Grant Edwards
2010-09-07 12:24 ` John Blinka
2010-09-07 12:29 ` Alan McKinnon
2010-09-07 13:11 ` Eray Aslan
2010-09-07 21:23 ` Jake Moe
2010-09-07 21:34 ` Alan McKinnon
2010-09-05 15:55 ` [gentoo-user] " Al
2010-09-07 21:48 ` Alan McKinnon
2010-09-07 23:09 ` Paul Hartman
2010-09-08 0:01 ` Alan McKinnon
2010-09-08 15:24 ` [gentoo-user] " Grant Edwards
2010-09-08 15:40 ` Alan McKinnon
2010-09-08 16:53 ` Per-Erik Westerberg
2010-09-08 20:06 ` Alan McKinnon
2010-09-08 20:14 ` Grant Edwards
2010-09-08 20:59 ` Alan McKinnon
2010-09-08 20:27 ` Paul Hartman
2010-09-08 20:54 ` Alan McKinnon
2010-09-08 20:22 ` Paul Hartman
2010-09-08 16:12 ` Paul Hartman
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=yu9bp8ajxp0.fsf@nyu.edu \
--to=gottlieb@nyu.edu \
--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