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

    • If Valve refused to let them make the case, I wonder if they've already partnered with someone else to do it? The fact that they didn't seek permission/licence before diving straight in is incredible though
    • OpenClaw now has native mobile apps on iOS and Android by Karthik Mudaliar OpenClaw, the viral open-source personal AI agent, now has its own mobile app, available on both Android and iOS. Users can pair the app with an existing OpenClaw gateway and can start using new mobile-native features that are now available on the app. The app supports all the existing features you'd already have seen on OpenClaw's TUI, as well as some more, such as real-time and background Talk mode, action approvals, sharing from iOS, and optional access to device capabilities such as camera, screen, location, photos, contacts, calendar, and reminders. These features are available on both the Android and iOS versions of the app. What's important with these apps is that they don't run OpenClaw on your phone, but are actually just companion apps that require a running OpenClaw Gateway on an existing device, on macOS, Linux, or Windows via WSL2. To pair the app with your existing OpenClaw gateway, users need to run the command "/pair qr" on the TUI or existing chat interface, which brings up a QR code. Users can then scan this QR code to pair it up with the mobile app. There's also an option to manually pair the app by entering the host and a port. Previously, OpenClaw had been available on phones via WhatsApp, Telegram, Slack, Discord, Microsoft Teams, Matrix, and others. Now, with a native mobile app, the interface is much cleaner and more focused on just the OpenClaw, of course, with the added support for camera, screen, location, and more. It's important to note that OpenClaw comes with its own security warnings. There's always a chance of prompt injection with these tools, so users are recommended to double-check authentication, tool policy, sandboxing, and execution approvals rather than prompts alone. For users well-versed with the AI harness, a native mobile app makes it easier to approve an automation, share a link, use voice, or let an agent react to phone-side context.
    • Google pitches Spanner as one database for all AI agents with these new featues by Karthik Mudaliar Google Cloud is introducing new features within Spanner, its distributed database, as a place where enterprises should keep their data, using which AI agents could make smarter and better decisions. In a detailed blog post, Google highlighted quite a few features coming to Spanner, including relational data, graph relationships, vector search, key-value access, full-text search, and operational analytics together in one database architecture. Google says that today's systems aren't well-made for AI agents. There could be data that is present in one system, search indexes in another, embeddings in a vector database, and relationship data in a graph database. This fragmentation isn't great for AI agents to do their jobs because they don't have access to all of this data in one place. This is where Google is positioning Spanner as a solution. Spanner is already a globally distributed relational database with strong consistency, and Google wants its customers to see it as a broader data layer for AI applications. The company introduced something called Spanner Graph, along with integrated vector search, full-text search, a Cassandra-compatible key-value endpoint, and a columnar engine for analytical queries on operational data. Google also added that its ScaNN-powered vector search can support indexes with more than 10 billion vectors, while the columnar engine can make some analytical scans up to 200 times faster. All of this isn't just exclusive to the Google Cloud Platform, and there's support for multi-cloud as well. This comes via Spanner Omni, which Google says is a downloadable, containerized version of Spanner that can run on Kubernetes and in environments outside Google Cloud, including Microsoft Azure and AWS, and even on-premises infrastructure as well as edge deployments. Google says that customers who are interested in the full-featured edition should contact the company, and there's no word on commercial availability or separate pricing. Those interested can read the full blog by Google Cloud, which details these features individually.
    • Kalmuri 4.2.5 by Razvan Serea Kalmuri is your all-in-one, portable screen capture and recording solution designed for speed, simplicity, and flexibility. Whether you need a full-screen snapshot, a custom area, a scrolling webpage, or smooth video recording, Kalmuri delivers with ease. Capture text instantly from images with built-in OCR, keep floating images on top for quick reference, and use the precise color picker for perfect design matching. Customize hotkeys to work your way and share results instantly with built-in upload options. Kalmuri runs without installation, making it ideal for USB use, and offers an intuitive interface that’s easy to learn. Kalmuri key features: Video recording support (designation of whole screen and area) Whole screen, active program, window control, area application Extract text from images using optical character recognition (OCR). Support for PNG, JPG, WEBP, BMP, GIF file formats MP4 video recording powered by FFmpeg for high-quality results Full web page capture Share the captured image on the web Color extraction function Printer output Hotkey settings Adjustable via keyboard for area capture (Arrow key, Ctrl+Arrow key, Shift+Arrow key) File name format (sequential, datetime) Free to use it at work, at home, in government offices, at school, etc. Using Kalmuri portable for video recording Kalmuri’s portable version doesn’t include FFmpeg, which is required for video recording. Without it, you’ll get an “error FFmpeg.exe not found” message. To fix this, download FFmpeg from the provided link, extract it, and place FFmpeg.exe in Kalmuri’s folder. Kalmuri will then recognize it automatically, allowing you to start recording in high quality instantly. Kalmuri 4.2.5 changelog: Fixed an intermittent crash when using Area Capture Improved stability for Area Capture and screen recording Resolved a capture issue that could occur right after startup Download: Kalmuri 4.2.5 | 24.2 MB (Freeware) Download: Kalmuri Portable 4.2.5 | 2.1 MB View: Kalmuri Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      rosiecharles earned a badge
      First Post
    • Reacting Well
      Juan Dela earned a badge
      Reacting Well
    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      273
    3. 3
      PsYcHoKiLLa
      143
    4. 4
      Steven P.
      98
    5. 5
      macoman
      54
  • Tell a friend

    Love Neowin? Tell a friend!