Linus Torvalds: 2560x1600 Needs To Be Next Standard


Recommended Posts

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.

Actually his view is spot on - I'd take a bigger 16:9 monitor over a smaller 16:10 monitor because I don't lose vertical space, but do gain horizontal space.

I have made the move (24" 16:10 1920x1200 to 27" 16:9 2560x1440) and don't find doing real work more jarring.

Holy Penguin is just like Woz - lost touch with reality a long time ago. I guess living on donations of big tech companies to grep stuff all day does that to people.

(companies that happen to get that money by constantly going against every principle he himself appears to stand for)

And, like many of his followers, he forgets that for most other people stuff like huge pixel matrices cost hell lot of money to buy. And it's not like it's coming cheap for companies, too - phones and schmablets have become half-thousand/euro/pound (and more) devices. Except that a great many of them are being sponsored by telcos - that can afford it because they then proceed to suck raw money out of their customers. Laptops for the most part don't have that kind of deals, so they're not getting hi-def screens either and that's all there is to it.

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.

In other words, you can't actually explain it. My post thoroughly went through why aspect ratio doesn't matter in the context of editing 16:9 video. But you've decided you're right, and you're clearly a very stubborn person.

However, no amount of your insulting personality or superiority complex changes the fact that I can buy two 2560x1440 monitors for a minimally higher cost than one 2560x1600 display, and you can't name one single use case where that one display does a better job than those two displays.

In fact, I seriously doubt you can do anything but insult people. Faced with the challenge of actually constructing an argument, you realize you have nothing to say, and instead of dealing with the fact that you simply haven't put much thought into the topic, you're taking the low road, insulting people, and feeling like it makes you the better person.

Spoiler: you can't win an argument without actually making one first. Reload from last save and try again.

If he's saying "stop with the retina crap" he doesn't understand what the concept of retina is. It's not JUST higher resolution. It's higher DPI. There's a very distinct difference. Higher res is all well and good, but a simple higher resolution mode means tiny text and icons. No one wants that. We need to have these useable. So retina display means fully useable but with more pixels per inch. Smoother text and icons.

However, I love that the Macbook Pro Retina runs at 2880x1800 constantly. No matter what 'mode' you're in. I use the 'looks like 1920x1200' mode. It's the kind of size of icons and text you'd get at 1920x1200 but of course, is on Retina, therefore being drawn at 2880x1800, which means it's super crisp. As smooth and beautiful looking as the regular mode.

So yeah ... higher resolution as standard? No. Higher DPI as standard? Well, Apple's likely to make that the case next year ;)

In other words, you can't actually explain it. My post thoroughly went through why aspect ratio doesn't matter in the context of editing 16:9 video. But you've decided you're right, and you're clearly a very stubborn person.

However, no amount of your insulting personality or superiority complex changes the fact that I can buy two 2560x1440 monitors for a minimally higher cost than one 2560x1600 display, and you can't name one single use case where that one display does a better job than those two displays.

In fact, I seriously doubt you can do anything but insult people. Faced with the challenge of actually constructing an argument, you realize you have nothing to say, and instead of dealing with the fact that you simply haven't put much thought into the topic, you're taking the low road, insulting people, and feeling like it makes you the better person.

Spoiler: you can't win an argument without actually making one first. Reload from last save and try again.

You're arguing about pixels, when it's an argument about dimensions. You just don't get it.

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

    • No registered users viewing this page.
  • Posts

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • 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
  • Popular Contributors

    1. 1
      +primortal
      455
    2. 2
      +Edouard
      206
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      68
  • Tell a friend

    Love Neowin? Tell a friend!