‹ BackHN Continuity

Thread

I said no and Apple said yes

886 points · 701 comments · thatslast

  1. vitro · · focus · HN ↗
    Not trying to start flamewars, but more and more I wonder how much are people willing to put up with such practices. On linux for 15+ years and everytime I try to use mac or win, it is an ordeal. And ads. F*cking ads in a system someone has purchased. And spying. Really user hostile environment. No, thank you.
    1. cosmic_cheese · · focus · HN ↗
      Because Linux is full of sharp edges which nobody seems to find it fit to fix.

      I’ve been dabbling in Linux since the early 2000s with Yellow Dog, SUSE, and Ubuntu, tried making it my daily driver in the early-mid 2010s, and for the past 5 or so years have been using it in a secondary/tertiary role.

      Recently I’ve been trying to move my gaming box from Windows to Fedora (which I’ve found mostly makes the right tradeoffs to suit my preferences). I’ve gotten things to mostly work, including games that have been blockers in the past, but just yesterday my ethernet connection listing disappeared and broke network connectivity. No big deal I thought, just go into settings and add it back, but as it turns out the KDE settings UI for NetworkManager is horrifically flaky and most critically, its add interface wizard doesn’t set correct settings for a successful connection. No, you have to drop down and use nmcli afterwards to fix things because the UI also doesn’t surface the right checkbox. I wouldn’t have even figured that out if it hadn’t been for a chatbot’s assistance.

      This is the exact sort of time-burning nonsense that isn’t a problem on either of the commercial platforms that I tend to encounter under Linux. Is this single instance going to push me to reboot that box back into Windows? No, but if issues like that keep cropping up eventually one will become the straw that breaks the camel’s back. Desire to avoid continued frustration will win over the logical portion of most peoples’ brains.

      1. arcanemachiner · · focus · HN ↗
        These sharp edges are a lot less annoying with agents to help solve the problem.
        1. cosmic_cheese · · focus · HN ↗
          Perhaps, but even as someone who uses LLMs I don’t like them being allowed to run amok on my machine. I don’t trust them.

          They’re also a crutch that shouldn’t be necessary for tasks so commonplace and simple as adding a network interface.

          1. treis · · focus · HN ↗
            They're the next step in UI for computers. Telling codex to add a network interface is easier than a GUI which is easier than a terminal program which is easier than manually editing a config file. None of those are a crutch. They are increasingly useful tools.
            1. advael · · focus · HN ↗
              Frankly I find terminal applications considerably easier than most GUIs for most purposes, but I agree that natural language are generally an easier interface layer than either, and that an interface layer to the functions of a computer in general seems to be their destiny as a technology
              1. cosmic_cheese · · focus · HN ↗
                I’ve been using command lines for over 25 years now and the thing that rubs me the wrong way about them is that nobody can agree on conventions with regard to how a CLI utility should work, which limits the amount of knowledge that’s transferable between them. Each effectively has to be learned individually which gets old fast.
                1. advael · · focus · HN ↗
                  I mean I think there's about as much convention and overlap as there seems to be for GUIs at least, and with much more discoverable clarification to boot
                  1. cosmic_cheese · · focus · HN ↗
                    The issue with manpages is that they need to be pulled up independent of the program, they’re overly verbose, and often don’t include practical usage examples or if they do, bury them under miles of flags I’ll never use.

                    Sometimes CLI utility help commands fill the gap, but often they’re too spartan or don’t even exist.

                    1. advael · · focus · HN ↗
                      Sure, documentation could always be better. My first attempt is usually tab-completion in the shell, then I'll try --help or something, then I usually go to either the archwiki or web search, which increasingly these days is equivalent to asking a chatbot, or asking a chatbot. I find I'm generally not getting past the --help part of that more than 10% of the time, and the web or wiki search solves my problem with one query 99.99% of the rest of the time, but I'm willing to believe this is aided by experience.

                      No amount of experience using GUIs stops me from about 40% of the time having to find a youtube video that explains what arcane path I need to take through a menu to find a setting, and if the menus have changed I might have to find the part of the video that explains what I'm looking for, watch it, realize it's changed, and hope I can find a more recent one. This goes for both native and web applications, for mobile and desktop, for every operating system I've ever touched

            2. rstupek · · focus · HN ↗
              I'm curious how you get codex to do anything when you don't have a working network?
            3. bigstrat2003 · · focus · HN ↗
              In no way is a stochastic system that has zero ability to understand anything "the next step in UI". That's a recipe for disaster and even greater frustration.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.