Linus Torvalds: 2560x1600 Needs To Be Next Standard


Recommended Posts

Try disabling font anti-aliasing and you'll quickly start seeing individual pixels.

But we have anti-aliasing? Doesn't really answer my question. I suppose I could see AA becoming irrelevant with it, but any gains from turning off AA would be lost with rendering at an increased resolution. So I still don't really see the point unless the performance gain from no AA outweighs the loss from resolution.

I find it hard to believe it makes any actual difference to viewing photos either. Unless it can mysteriously extract additional pixels from the photo data, all it would do is "zoom out" the photo.

He is right, but the OS must be able to scale with the resolution. I don't want everything to be too small to read because of the crazy resolution. Apple and Google seem to be making a good job at scaling iOS and Android to fit any resolution and still being usable.

But yes, when I see that my Galaxy S3 has more pixels than some laptop, it's getting ridiculous.

You could even have a 10000dpi display but until desktop operating systems will do proper DPI scaling on very high resolutions displays it's completely pointless.

Windows scaling starts looking horrible from 200% DPIs and above (cursors and icons all look jagged) and there are still many applications that look horrible or ignore the scaling like Adobe's (also DPI settings seem to be ignored by Metro), OS X cheats by upscaling a lower resolution unless the application is "retina-aware" and Linux is probably the one with most issues but it depends, it can be either somewhat acceptable or horrible depending on the distro/desktop environment.

It is actually quite funny that it was Linus Torvalds complaining about this issue when most linux distributions recommend lowering the resolution on the retina macbooks basically tossing the extra pixels in the trash. If it's not done properly it just becomes a waste of CPU/GPU/power: it would be far better to have a reasonable resolution (1080p minimum?) that works well with the operating system rather than some insanely high-DPI display where everything looks like crap and movies still show with the annoying bars due to weird aspect ratios.

I think Apple approach was the best because they always tried to double the resolutions on their devices to make the transition the least painful they could and on the retina display their use of a whitelist system (only tested applications will work in native mode) has avoided the issues with all the applications that don't render properly. I still wonder why Windows still uses the cheapest scaling algorithms for some parts the UI, it's not like the recent CPUs couldn't scale a 32x32/48x48 cursor.

NOTE: This post is only exclusively about desktop operating systems, not phones or tablets where the UIs have been tailored for DPI scaling from the start.

But we have anti-aliasing? Doesn't really answer my question. I suppose I could see AA becoming irrelevant with it, but any gains from turning off AA would be lost with rendering at an increased resolution. So I still don't really see the point unless the performance gain from no AA outweighs the loss from resolution.

I find it hard to believe it makes any actual difference to viewing photos either. Unless it can mysteriously extract additional pixels from the photo data, all it would do is "zoom out" the photo.

That's kind of the point, we're using anti-aliasing (for nearly everything) because we have such low resolution devices. Increasing the resolution negates the need for anti-aliasing. Photos see an improvement since they're often scaled down for display, showing them at their normal resolution allows for more fine detail.

Compare proper 1920x1080 video to a scaled 960x540 copy, the overall image will be the same, but you'll be missing out on fine detail.

I'm really not sure I understand this trend of squeezing more pixels into the same physical space. Have we suddenly evolved to have mega awesome eyes that can see individual pixels at 5 feet away? :wacko: Using my computer, netbook or phone I can't see the individual pixels unless my eyes are too close to the screen. Maybe I'm not understanding something but it seems like pointless number increases to me, much like camera megapixels.

The point is that breaking the 300 PPI barrier supposedly makes it nigh on impossible to see individual pixels, even at close range. For devices like tablets that are usually used pretty close up it will make a difference.

The point is that breaking the 300 PPI barrier supposedly makes it nigh on impossible to see individual pixels, even at close range. For devices like tablets that are usually used pretty close up it will make a difference.

On a smartphone or tablet it definitely makes sense and you can clearly see the difference. However, I'm using my 27-inch iMac at a comfortable 50 cm away and it already becomes increasingly hard to see the individual pixels. I have no doubt a "retina" iMac will be nicer, but the issue isn't as pressing as on - let's say - an iPhone.

And we'll pay out the rear for it. I can't see a huge difference between my desktop running 1280*1024 (19" CRT) vs my laptop running 1366*768 (15.6"). Maybe it's my need for glasses that blinds me, or it's just a big marketing scam like most crap is.

The standard should be 300ppi for mobile hardware (phones and tablets) and 150ppi for computers (laptops and desktops), considering you're usually not holding the second two close to your face so there's no need to push it as far as mobile devices go. Just think of the clear text and the eyes saved if this was to become a standard.

Right now I'm using a 24" LG @ 1080p, the pixel grid is visible from where I'm sitting if I lean just a bit towards it.

The standard should be 300ppi for mobile hardware (phones and tablets) and 150ppi for computers (laptops and desktops), considering you're usually not holding the second two close to your face so there's no need to push it as far as mobile devices go. Just think of the clear text and the eyes saved if this was to become a standard.

Right now I'm using a 24" LG @ 1080p, the pixel grid is visible from where I'm sitting if I lean just a bit towards it.

I'd argue 330+ for mobile devices, 270+ for laptops, 200+ for desktop displays.

Currently I have:

iPhone 4: 960x640 @ 326ppi (and really good during normal operation)

Nexus 7: 1280x800 @ 216ppi (noticably lower than the iPhone) - this would be better in 330ppi range for day to day usage.

Thinkpad Edge 11: 1366x768 @ 135ppi (unacceptably low) - I would be very happy if this was in the 270ppi range for day to day usage.

Dell U2711: 2560x1440 @ 109ppi (low but marginally better than the Thinkpad) - it would be better if this was in the 200ppi range for day to day usage.

I'm more in line with these later opinions that understand PPI values should vary depending on device type. Resolution is not a simple matter of pixels and PPI. Anyone who establishes their opinion on display standards with just these two values does not understand display ergonomics.

At the lowest level, you want to begin with how far your eyes are from the screen. A smartphone, laptop, desktop, and television are all viewed at different distances--and even then, those distances aren't common for all people. You might sit comfortably anywhere from 1'-2.5' from your laptop display while doing work. Pixel density will have dramatically different effects depending on where you fall in this range.

Once you establish your comfort zone with displays, you need to determine which range of PPI values match it. That is, which PPIs make pixels indistinguishable at the high and low end of this zone (turn off font smoothing if you want to get really serious about it, but at that point you're going beyond what reality will ever throw at you--your choice). Hang on to these two values, because you can map these against the final cost of the display when you make your decision.

Now, take your preference for aspect ratio. Throw it away. It's meaningless. It doesn't matter. It's one of those things people take way too seriously and defend to the death with nothing but flawed anecdotal evidence and studies on FoV they don't even understand. What matters is perceived space. A 24" 16:9 display will have just as much physical vertical space as a 23" 16:10 display, and cost the same or less simply because 16:9 panels are in higher demand. It's not a matter of losing vertical space with 16:9--you're gaining horizontal space.

It's a lot easier to wrap your mind around if you give these two ratios a common denominator. It isn't about 16:10 vs. 16:9 (where the vertical value appears lower). It's 160:90 [16:9] vs. 144:90 [16:10]. This more accurately represents what you get for your dollar.

Now, ask yourself what the vertical height was of the 16:10 display you so fell in love with, and find out what diagonal length a 16:9 monitor has to be to have the same vertical height. Make this your minimum display size.

At this point, you know the physical size of the monitor you want, and the pixel densities to match. Congratulations, you have an informed opinion.

/my 16:9 27" 2560x1440 monitor lets me see more than your 1920x1200 16:10 display ever will, so come off it already. AR doesn't matter.

I think he's right. It's kind of ridiculous to have a 1280x720 (and higher) screen res. on a 4.5" phone, yet have a laptop's 13" screen be only 1366x768px. Maybe the screens don't need to be 2560x1600, but at least have 1600x900 instead of 1366x768.

/my 16:9 27" 2560x1440 monitor lets me see more than your 1920x1200 16:10 display ever will, so come off it already. AR doesn't matter.

The extra space on the top and bottom is useful for us that create and edit 16:9 content. Congratulations, you've completely missed the point of 16:10.

The extra space on the top and bottom is useful for us that create and edit 16:9 content. Congratulations, you've completely missed the point of 16:10.

You're being snarky, but for making it to the bottom of my post, you completely missed the point.

Think, for a second, in terms of actual physical space: actual inches in the physical real world. A 23" 16:10 display gives you extra vertical space to work on 16:9 video, yes. But a 24" 16:9 display gives you the same extra vertical space, PLUS extra horizontal space, while the amount of actual physical space the video takes up on the screen is the same.

THAT is my point. Aspect ratio doesn't matter when the fact is a PHYSICALLY LARGER display is more affordable at 16:9 than 16:10. Let me actually draw a picture for you, because I think this is something people are genuinely having trouble making their brains process. Note that the attached picture is to compare the two aspect ratios where the video frame is given the exact same real-world physical space. You have the exact same space for the video frame, the exact same extra vertical space for editing controls, plus bonus extra horizontal space for whatever you desire, all on a monitor that costs the same price. You only lose the extra vertical work space if you decide to give the video frame more physical area, but at that point you'd need a physically even larger 16:10 display, which would add to the pricetag, and--guess what--a larger still 16:9 display will be available yet again at that same new higher price.

Entirely because of the effect TV panels are having on the cost of displays, it remains economically feasible to always just buy a LARGER 16:9 monitor that can contain the same work space as the smaller 16:10.

This is very, very simple math here. Middle school level stuff. Please, please tell me this isn't still going over your head.

/something to think about: for 2560px wide displays, 16:9 will run you $700, 16:10 will run you $1200. you can either pay $500 dollars for those extra 160px in height, or buy two of the 16:9 monitors. $1200 for 2560x1600, or $1400 for 5120x1440. I would rather buy two slightly shorter displays than be punished with a 50% markup per pixel for one slightly taller display. In pure economical feasibility, telling yourself that 16:10 is the "better choice" is downright lunacy.

post-10281-0-84041300-1351972610.png

It's not about math, it feels unwieldy and doesn't work. You're missing the human element here.

Hang on here. I'm going into extreme detail to communicate my point of view, and all you're going to do is throw out a subjective remark like "it feels unwieldy" and conclude that it therefore "doesn't work"?

I see once you decide to believe something, you completely shut yourself off to even processing contradictory information. Can you even explain why it "doesn't work"? Or do you just say things and expect to be right by virtue of Having Spoken?

Hang on here. I'm going into extreme detail to communicate my point of view, and all you're going to do is throw out a subjective remark like "it feels unwieldy" and conclude that it therefore "doesn't work"?

I see once you decide to believe something, you completely shut yourself off to even processing contradictory information. Can you even explain why it "doesn't work"? Or do you just say things and expect to be right by virtue of Having Spoken?

Your point of view is nonsense, extreme detail, or otherwise. If it doesn't take you 5 seconds to realize the practical benefits of using a 16:10 monitor to edit 16:9 frames, then you're just dense.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft is bringing a much-needed Recap app to Teams, here is a first look by Usama Jawad Microsoft Teams is heavily used in work and school environments, and perhaps one of its core but extremely useful features is the ability to record meetings. In past years, Microsoft has further improved upon this functionality by integrating AI, but you do need a Microsoft 365 Copilot license to leverage most, if not all, all of those capabilities. Now, the Redmond tech firm is making another significant enhancement in the area of Teams meeting recordings. Up until now, if you wanted to access Teams recordings, you had to arduously locate the meeting invite and navigate to the dedicated tab, or go to the cloud storage location such as a SharePoint site. This was a rather overwhelming activity, especially if you don't remember the name of the meeting or the meeting occurred quite a while ago. Microsoft is now attempting to solve this problem through a dedicated Recap app that consolidates all your recordings. This centralized experience will allow users to find all recordings from the past 30 days and also offer access to other related services such as transcripts and AI-powered summaries. Customers will have the option to search for recordings, filter them, and review multiple meetings by generating AI-powered podcast-style recaps. The Recap app will list all available recordings in both thumbnail and list views. The former is shown below: And here is how Teams users with a Microsoft 365 Copilot license can select multiple recordings to generate a podcast-style audio recap: Microsoft has emphasized that the Recap app is pre-installed in Teams but it will not be pinned by default. Users will able to navigate to the Teams app store from the left rail, and pin it from the apps section. It will be enabled by default for all users once it becomes available. It's worth noting that while Teams recordings and transcripts can be accessed by all users governed by existing permissions, AI-powered features like intelligent summaries, audio recaps, and video recaps will require a Microsoft 365 Copilot license. The Recap app will be generally available to Teams users on Windows, Mac, and the web by the end of next month, with mobile support coming soon.
    • It's so stupid that you have to "enroll" in these extended updates.
    • Helium Browser 0.13.6.1 by Razvan Serea Helium is a private, fast, and honest Chromium-based web browser — built for people, with love. It offers the best privacy by default, unbiased ad-blocking, and a clean experience free from bloat and noise. Proudly based on Ungoogled-Chromium, Helium removes Google’s clutter while keeping a fast, efficient development pipeline. With thoughtful touches like native !bangs and split view, Helium is a people-first, fully open-source browser that puts control back in your hands. Privacy, security, and control come first. Ads, trackers, and third-party cookies are blocked automatically, HTTPS is enforced everywhere, and all Chromium extensions work seamlessly — while Google can’t track your activity. Helium’s 13,000+ offline-ready !bangs let you jump straight to sites or AI tools like ChatGPT instantly. Open-source, people-first, and unbiased, Helium delivers a browsing experience that’s fast, secure, and free from noise, ads, and compromises. Helium Browser key features: Performance Fast, efficient, and lightweight — built on Chromium’s optimized engine. Energy-saving and consistent — stays fast over time without slowing down. No bloat — stripped of unnecessary components for maximum speed. Minimalist interface — compact, clean, and distraction-free. Customizable toolbar — hide elements you don’t need. Smooth and stable — no flicker, lag, or animation glitches. Comfort-focused experience — intuitive and unobtrusive. Privacy & Security Best privacy by default — blocks ads, trackers, phishing, and third-party cookies. Unbiased ad-blocking — powered by community filters and uBlock Origin. No telemetry or analytics — zero background web requests on first launch. Strict HTTPS enforcement — warns for insecure sites. Passkeys supported — modern authentication made simple. No built-in password manager or cloud sync — your data stays yours. Extension Compatibility Full Chromium extension support — including MV2 extensions. Anonymized Chrome Web Store requests — Google can’t track extension installs. Extended MV2 support — maintained for as long as possible. Smart Features Native !bangs — browse faster using 13,000+ offline-ready shortcuts. AI integration — use !chatgpt and others directly from the address bar. Offline functionality — bangs work without an Internet connection. Philosophy People-first design — open source, transparent, and community-driven. No ads, no noise, no bias — privacy and honesty over profit. Helium Browser 0.13.6.1 changelog: c6feb7e0 revision: bump to 6 (#2015) 03a16cfa merge: update to chromium 149.0.7827.200 (#2014) d447f889 merge: update ungoogled-chromium to 149.0.7827.200 8f30897f Update to Chromium 149.0.7827.200 1772f7ce bump-platform: check if b/s/chrome exists instead of just b/s/ (#2003) Download: Helium 64-bit | Portable 64-bit |~100.0 MB (Open Source) Download: Helium ARM64 | Portable ARM64 Links: Helium Home Page | macOS | Linux | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too late for a slightly older computer I had that didn't meet the hardware requirements for Windows 11 but had great hardware. I installed ubuntu on that thing and gave to a friend's kid.
  • Recent Achievements

    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
    • First Post
      Kolakid60 earned a badge
      First Post
    • Week One Done
      xvvxcvv earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      424
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      149
    4. 4
      Steven P.
      71
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!