Try Pulseway for free and start remotely monitoring and managing your server or PC at https://lmg.gg/Ktd7ZUse code LINUS and get 25% off GlassWire at https:/...
The second episode of LTT’s Linux challenge is out.
I think the series is good, and also important. Especially that it shows that Linux can also be used for gaming.
What bothers me a bit, however, is that a barrel is sometimes opened due to operating errors or false expectations. Such as the file extensions. Linux actually don’t use the file extensions, it never has, but have so “naturalized” by the users. The exotic setup of Linux is also often left under the table. Hardly anyone has their PC in a 19" rack in another room.
With his setup, I’m amazed that anything is working at all. It’s impressive that it’s working as well as it is.
And yeah, the false expectations part. It’s a pitfall for most people. It would actually be really interesting to watch someone who only grew up using Linux try and switch to Windows. I wonder how much more or less confusing it would be to them. That would be a good way to compare what is a true problem and what is just expectations. Windows has tons of quirks and bad design that people have normalized and learned to live with and have become non issues.
It would actually be really interesting to watch someone who only grew up using Linux try and switch to Windows.
For sure!
Like another commenter was saying too, they are just applying a Windows mentality on a Linux installation. If you go with a Windows mentality to macOS you’ll also have issues and vice-versa. The view they are showing isn’t great…
It’s also clear Luke has knows what his doing more than Linus, so at least we’re seeing a less confusing side of the story.
The exotic setup of Linux is also often left under the table. Hardly anyone has their PC in a 19" rack in another room.
Aside from the Thunderbolt connection maybe not getting proper driver support (because Intel sucks with open source), I don’t see the problem with this. Linux is very widely used in servers, embedded systems, and digital signage, all of which have more challenging display/input setups than Linus’s setup.
For someone who knows what he does, it’s no problem. But for a beginner?
Server run headless. So no monitor. Embedded systems mostly have their display directly onboard or have none, like the APU/ALIX Boards. And all of them have other usages than gaming.
Well, servers can also have software remote displays, display over ethernet or IPMI, or KVM switched displays. Digital signage may place the display many meters away from the computer in an outdoor electrical box, could well require a mosaic of displays over many ports to make a huge image, and can also be interactive through a large touchscreen or other sensors. Digital signage can sometimes also require pretty substantial graphics processing if the effective resolution is huge or if it’s highly reactive or interactive with many animations. Embedded devices can have irregularly shaped displays, weird interfaces, or again, multiple displays. Linux has excellent solutions for all of them, so I find it hard to believe that a remote PC environment connected through Thunderbolt would challenge it, barring a driver issue (which, again, would be Intel’s fault since Thunderbolt is proprietary to them, not a problem with Linux per se).
I think the series is good, and also important. Especially that it shows that Linux can also be used for gaming.
What bothers me a bit, however, is that a barrel is sometimes opened due to operating errors or false expectations. Such as the file extensions. Linux actually don’t use the file extensions, it never has, but have so “naturalized” by the users. The exotic setup of Linux is also often left under the table. Hardly anyone has their PC in a 19" rack in another room.
With his setup, I’m amazed that anything is working at all. It’s impressive that it’s working as well as it is.
And yeah, the false expectations part. It’s a pitfall for most people. It would actually be really interesting to watch someone who only grew up using Linux try and switch to Windows. I wonder how much more or less confusing it would be to them. That would be a good way to compare what is a true problem and what is just expectations. Windows has tons of quirks and bad design that people have normalized and learned to live with and have become non issues.
For sure!
Like another commenter was saying too, they are just applying a Windows mentality on a Linux installation. If you go with a Windows mentality to macOS you’ll also have issues and vice-versa. The view they are showing isn’t great…
It’s also clear Luke has knows what his doing more than Linus, so at least we’re seeing a less confusing side of the story.
Aside from the Thunderbolt connection maybe not getting proper driver support (because Intel sucks with open source), I don’t see the problem with this. Linux is very widely used in servers, embedded systems, and digital signage, all of which have more challenging display/input setups than Linus’s setup.
For someone who knows what he does, it’s no problem. But for a beginner?
Server run headless. So no monitor. Embedded systems mostly have their display directly onboard or have none, like the APU/ALIX Boards. And all of them have other usages than gaming.
Well, servers can also have software remote displays, display over ethernet or IPMI, or KVM switched displays. Digital signage may place the display many meters away from the computer in an outdoor electrical box, could well require a mosaic of displays over many ports to make a huge image, and can also be interactive through a large touchscreen or other sensors. Digital signage can sometimes also require pretty substantial graphics processing if the effective resolution is huge or if it’s highly reactive or interactive with many animations. Embedded devices can have irregularly shaped displays, weird interfaces, or again, multiple displays. Linux has excellent solutions for all of them, so I find it hard to believe that a remote PC environment connected through Thunderbolt would challenge it, barring a driver issue (which, again, would be Intel’s fault since Thunderbolt is proprietary to them, not a problem with Linux per se).