<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Hammers Without Handles: Why Linux UX Sucks.</title>
        <link>https://subscribeto.me/videos/watch/039068b0-a32f-4131-8b52-086c2fed401f</link>
        <description>Inspired by LinusTechTip's latest Linux Daily Driver Challenge, I wanted to take a moment and talk about Linux UX because, let's face it... it sucks. Actually, it's worse than that. Much of Linux's UX is technically correct and that makes it objectively wrong. Like it or not, Windows is the dominant operating system. And it's not even close. That means when we're having a conversation about designing a User Experience on Linux-based operating systems, that conversation must be bookended by "how do Windows users expect this to work?" And we need to design for that or else everything falls apart. https://gardinerbryant.com/hammers-without-handles-linux-ux-sucks/ 00:00 Linux User Experience sucks 01:47 Mounting Network Shares on Linux is a horrible experience 03:21 The Fix 03:50 The Noise Brigade will argue against this 05:09 Why we need to solve these issues 06:07 GNOME Disks UX Fail 09:01 The Noise Brigade responds 10:42 Disks fails twice, though... 13:04 Hammers Without Handles</description>
        <lastBuildDate>Fri, 05 Jun 2026 07:22:22 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>PeerTube - https://spectra.video</generator>
        <image>
            <title>Hammers Without Handles: Why Linux UX Sucks.</title>
            <url>https://spectra.video/lazy-static/avatars/71f5d173-eea9-47a7-b254-f7e91f9f5d25.png</url>
            <link>https://subscribeto.me/videos/watch/039068b0-a32f-4131-8b52-086c2fed401f</link>
        </image>
        <copyright>All rights reserved, unless otherwise specified in the terms specified at https://spectra.video/about and potential licenses granted by each content's rightholder.</copyright>
        <atom:link href="https://spectra.video/feeds/video-comments.xml?videoId=039068b0-a32f-4131-8b52-086c2fed401f" rel="self" type="application/rss+xml"/>
        <item>
            <title><![CDATA[Hammers Without Handles: Why Linux UX Sucks. - Maât]]></title>
            <link>https://spectra.video/w/1rwwJsdKFA7yt2ca1aqCee;threadId=59632</link>
            <guid>https://spectra.video/w/1rwwJsdKFA7yt2ca1aqCee;threadId=59632</guid>
            <pubDate>Fri, 05 Jun 2026 04:33:28 GMT</pubDate>
            <content:encoded><![CDATA[<p><span><a href="https://subscribeto.me/a/gbryant/video-channels" class="u-url mention" target="_blank" rel="noopener noreferrer">@<span>gbryant</span></a></span> </p><p>1) The original link : <a href="https://gardinerbryant.com/hammers-without-handles-linux-ux-sucks/" target="_blank" rel="noopener noreferrer"><span>https://</span><span>gardinerbryant.com/hammers-wit</span><span>hout-handles-linux-ux-sucks/</span></a></p><p>2) the idea of the mounting wizard is not a bad one</p><p>3) why hell did the author feel the urge to say linux UI suck instead of "hey guys i have an idea to improve this..."</p><p>4) CONTRIBUTION WELCOME ! Please provide your patch to Dolphin and Nautilus instead of badmouthing.</p>]]></content:encoded>
            <dc:creator>Maât</dc:creator>
        </item>
        <item>
            <title><![CDATA[Hammers Without Handles: Why Linux UX Sucks. - nwoof]]></title>
            <link>https://spectra.video/w/1rwwJsdKFA7yt2ca1aqCee;threadId=59629</link>
            <guid>https://spectra.video/w/1rwwJsdKFA7yt2ca1aqCee;threadId=59629</guid>
            <pubDate>Fri, 05 Jun 2026 01:27:18 GMT</pubDate>
            <content:encoded><![CDATA[<p>imo there are always two completely different directions when it comes to UI/UX. The first one is user specialized. This has the benefit of fitting the user like a fine glove, the downside is that the user should learn it and make it themselves. Therefore the useful thing to do in that case is to provide more tools for the user. It's obvious that's not useful for new users. The second one is to make something which most people already know. The obvious downside is that it's not that efficient for the skill user, because very opinionated decisions has to be made. The benefit is that the user is expected to already have the intuition for what to be expected. In that case the obvious path is to copy something well known. If you want to appeal to broad group of users you should use the second approach.</p>
]]></content:encoded>
            <dc:creator>nwoof</dc:creator>
        </item>
    </channel>
</rss>