• taiyang@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    3 months ago

    The most obvious bait to be was 1 hour install time. Windows 11 took 2 hours to install, CachyOS took like 5 minutes. I imagine Arch is similar, there is simply no way. Lol

      • rklm@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago

        Discover is ok… If you limit it to only managing Flatpaks.

        I’m not sure I’d ever trust a GUI to manage pacman/apt/dnf

        • kn33@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          I’m gonna be honest, 99% of what I need to do, I do through Discover. Like, why would I bother typing a command out when the update button is right there.

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 months ago

    #2 gave it away because you’d have to royally screw something up in Arch to get KDE to lag like that lol.

    It might be minimalist but it’s not unperformant out of box.

  • neukenindekeuken@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    The performance comments were a dead giveaway.

    Nobody’s complaints with setting Linux up are that it runs slowly.

    It may not run much of anything until you sort out your drivers properly, but it will do everything incorrectly LIGHTNING fast, compared to Windows.

    • baltakatei@sopuli.xyz
      link
      fedilink
      arrow-up
      0
      ·
      3 months ago

      I thought Debian was as sluggish as Windows until I was forced to use the LXQt desktop environment instead of the default GNOME on an old Compaq laptop since that’s all it could handle. Turns out, GNOME looks nice but it kept my old laptop’s mid-2000s i386 CPU churning at 50% 24/7. LXQt? Barely a blip. Sure, it couldn’t run Firefox quickly, but at least its fan was silent when idling or when I was simply using the laptop as a dumb SSH client into a much more powerful remote server.

      I now use LXQt on my main workstation because I don’t need fancy tilíng windows or Wayland.

      • rumschlumpel@feddit.org
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        3 months ago

        I now use LXQt on my main workstation because I don’t need fancy tilíng windows or Wayland.

        You can have fancy tiling windows and Wayland without Gnome! Wayland is actually pretty great for low-resource devices, I recently did a glmark benchmark on a Raspberry Pi 3B, and on the Wayland session (with the wayland version of glmark) I got about double the score of the Xorg session (with the xorg versioni of glmark). It’s just that Raspberry Pi OS’s Wayland session doesn’t use Gnome, but LabWC.

        And I always configure my LXQt desktop with a tiling wm, works great and looks great IMO. Plus, the LXQt devs are working on making it fully Wayland-compatible.

    • lemmyvore@feddit.nl
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Depends what kind of newbie. To the right kind of nerd a well-organized technical installer is not a deterrent, on the contrary.

      I don’t think people realise that most Linux distros had arcane install processes not unlike Arch until around 2000, when a few of them started introducing simplified graphical installers (Corel, Caldera and Red Hat’s Anaconda I think were most popular). Debian for instance only switched to graphical in 2006 with Etch beta 3 (although tbf they did have a text-mode UI before that).