The creator of the Linux kernel isn't quite as outspoken as other, more bearded members of the open-source community. He does speak out on occasion, though. His latest rant went up on Google+ earlier this week, and it's been spreading like wildfire. Here's a snippet:
So with even a $399 tablet doing 2560x1600 pixel displays, can we please just make that the new standard laptop resolution? Even at 11"? Please. Stop with the "retina" crap, just call it "reasonable resolution". The fact that laptops stagnated ten years ago (and even regressed, in many cases) at around half that in both directions is just sad.
Torvalds is, of course, referring to the inexplicably ubiquitous 1366x768 resolution that still plagues entirely too many notebooks. "[Expletive], soon even the cellphones will start laughing at the ridiculously bad laptop displays," he says.
This isn't exactly an uncommon sentiment, of course. We've been expressing it in our laptop reviews for years now. Still, it's nice to see a high-profile member of the industry speak out against crappy laptop screens.
At least some notebook makers have shaken themselves out of their torpor recently. Apple's new Retina MacBook Pro laptops have 2560x1600 and 2880x1800 resolutions at 13" and 15", respectively, while Asus' Zenbook Prime UX31A crams 1920x1080 pixels into its 13" panel. Too bad Windows 8's support for denser screens still leaves something to be desired, especially in the Modern UI interface.
|Silverstone's Strider Titanium PSUs are ready for a high-power future||11|
|VR180 video bridges the gap between YouTube and VR||0|
|Steam 2017 Summer Sale, part deux||15|
|Deals of the week: Z270 mobos, spinning storage, and more||4|
|G.Skill readies up for X299 with quad-channel DDR4 at 4200 MT/s||16|
|Asus' VivoBook S510 is an ultrabook for the budget crowd||16|
|Windows Insider Build 16226 gives users a look at GPU utilization||24|
|Steam's 2017 Summer Sale is downright hot||49|
|Asus XG-C100C NIC breaks the gigabit barrier||34|
|So are we any closer to figuring out what causes instability when large parallel compilations are run on Ryzen with the gcc toolchain? It sounds like...||+5|