Slashdot Mirror

"don't see the point in going up to even 22" on a desktop. To compensate for the slight increase in view distance maybe a 19", but no more"

You can't get 1920x1080 at 19" or 20", unfortunately. At least not that I've found. Standard res at 19" and 20" is 1600x900. Basically, it's just about impossible to buy a desktop monitor higher than around 100dpi: it's a barrier. If you look at where the resolution jumps happen, it's _always_ at around 100dpi. The smallest monitor you can usually buy these days is 18.5", some of which come at 1600x900, which is 99.23dpi. The jump to 1920x1080 comes at 21.5", that's 102.46dpi. The next standard jump is to 2560x1440 at 27", which is - oh hey! - 108.79dpi. Everything around 100-110dpi. You just can't buy higher on the open market. http://members.ping.de/~sven/dpi.html is a neat site I like - it has the DPIs of common sizes and various 'notable' displays. It's somewhat frustrating, though, as it provides details and links to various crazy professional high-res displays which cost thousands of dollars and were all discontinued years ago anyway. I had a Vaio P a while back, which was the champion of that list at 221dpi until the Retina displays started showing up...

It's difficult to get a really high quality 19" or 20" monitor. I picked the U2211 because it's the smallest of Dell's high-end line, with IPS panels and good build quality, color management, rotation etc. If they had a 20" model at 1920x1080 I'd go for it like a shot, but they don't, sadly.

Try playing with this tool for a while.

http://members.ping.de/~sven/dpi.html

I myself love having more space... However for most people they just complain that everything is too small. So for the most part the past decade in a half displays have been staying at the same DPI.

This is an important observation and possibly a major reason why the DPI of the displays has stayed low. The operating systems can't be adjusted to it. It kind of works but it's still a hack. I have a good vision but sometimes am annoyed by the small text of my 135 DPI laptop.

It is good though that Apple works as a pioneer to create this kind of hi-res stuff to challenge the problem!

As a bonus, here's a nifty DPI calculator.

http://www.ping.de/sites/systemcoder/necro/info/sumerfaq.htm

With references. Eat your heart out. Your religion absorbed akkado-Sumerian elements. Get over it. You didn't actually seriously think that Genesis was the first religious document ever written, ddid you?

Regarding to the using-a-TV solution, one thing worth noting is that unlike monitors, they don't usually have a tilt mechanism. That may be bad for ergonomics. You might end up needing to buy a separate stand which has it.

By the way here is a nice DPI calculator I found one day.

I wrote a script to automate the detection of wildcard domains, go ahead and download it. It requires the djbdns tools in the path (dnsqr and dnsq). It generates a list of all wildcard domains suitable for the djbdns wildcard ignore patch.

Notice I said "functional-programming types of paradigms", not functional programming.

It does have first-class functions (the Proc class) it's just that the syntax is driven towards making closures accessible instead of functions and creating Procs is a lot more involved.

On the other hand, what they do with the closures (a.k.a. Code Blocks) is quite amazing on its own merits. The concept of being able to iterate over arbitrary stuff in a variety of ways with them comes in quite handy, plus all of the other ways to make the language easier to deal with.

And, then of course, there's the functional library. ;)

This is a bug and it does allow someone to track where you're going. The proof of concept page clearly states that the "referer of the http request for this image will be the page you are visiting next , not this page " (emphasis is theirs). I expect that when JavaScript is executing for the page I am leaving, that it have no idea where I am going. Anything otherwise is a breach of privacy, and should be considered a bug.

Here is an easy fix,

1. In Mozilla goto ...
'Edit | Preferences | Advanced | Script & Plugins'

2. Uncheck the following checkboxes ...
'Ceate or change cookies' and 'Read Cookies'

After changing this goto the demo page again to verify! The demo will not work anymore.

Check out this example application designed with and for Mozilla and other standards compliant browsers.