public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: OT: advice sought on new laptop for Gentoo
Date: Mon, 6 Sep 2010 08:16:53 +0200	[thread overview]
Message-ID: <201009060816.53091.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <i619sh$gp9$2@dough.gmane.org>

Apparently, though unproven, at 01:42 on Monday 06 September 2010, Grant 
Edwards did opine thusly:

> >> Yup, and 16x9 sucks -- it's just an excuse to ship smaller,
> >> lower-resolution displays labelled with bigger numbers.
> >>
> >> 
> >>
> >> Complete ripoff.
> > 
> > If you have 16:9 at 1280*720, then yes, it is going to suck. There is
> > nothing  inherently wrong with the aspect ratio, please desist from
> > trying to make it so.
> 
> Yes, there is an inherent problem: in order to get what I consider
> acceptable vertical size/resolution you have to buy something that's
> rediculously wide.

Untrue.

Vertical resolution depends only on the available dimension and the number of 
pixels-per-inch of your screen.

How do you manage to take the position that screen height somehow depends on 
the machine width? Remember that we are talking regular sized notebooks here

> 
> > There are good reasons for it. It most easily fits the overall
> > dimensions of the machine, you have a wide and not very deep keyboard
> > plus space for a touchpad and palm rests. It's all approximately
> > 16:9.
> 
> No it's not.  At least only on any of my laptops.  I suppose you can
> tack on a useless numeric keypat to try to take up some of the extra
> horizontal space that's required in order to get a screen that's tall
> enough to be useful.

I have a 16:9 in a regular sized notebook, a Dell M1530. There's no numpad. In 
fact the keyboard takes up less space horizontally than I'm used to. 

So please tell me again where this machine width thing comes from?

> > I paid the extra to get 16:9 @ 1920x1200. Best thing I ever did
> > laptop-wise - I can get two webpages side by side on the screen
> > looking very natural.
> > 
> > Did you know that 16:9 is the eye's natural aspect ratio?
> 
> How do you explain the widespread popularity of portrait mode for
> printed material?  Text is much easier to read in tall, narrow,
> columns.  The more lines of code you can see at once when editing
> source code, the fewer the bugs.  Both those have been experimentally
> verified.

Tall narrow columns come from newsprint and the average person does not 
display only text on a screen. Even the example you cite - printed material - 
is incomplete, in that few folks have only one of them when working.

The usual case is one book for reference, and at least one other work area. 
Which is why I mentioned two web sites side by side at a very acceptable size.


> > Test it sometime with outstreched fingers.
> 
> I still vastly prefer 4:3 for all of the work I do.  I guess if you
> want to watch movies, and you don't mind hauling around a useless
> numeric keypad, 16:9 is nice.

Once again, who mentioned a numpad? I didn't. You inserted that the bolster 
your argument, but I never put it there.

Personally, I think you went cheap and bought a less-than-ideal screen based 
on price. I didn't make that error - I spent the extra bucks, sacrificed a few 
features here and there and went for the best on offer. I have full 1200 
height (the same as I get out of my 21" CRT monitor) which instantly renders 
all your arguments redundant.

So tell me again why there is something wrong with 16:9?

I think you have it conflated with 800 height which indeed is pathetic.


-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2010-09-06  6:21 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 [this message]
2010-09-06 16:24         ` Grant Edwards
2010-09-06 22:02           ` Mick
2010-09-06 22:48           ` Allan Gottlieb
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=201009060816.53091.alan.mckinnon@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