• mirtuevagnet@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    9 months ago

    Provide out-of-box ease of use on everyday devices operated by low-skilled users.

    I mean, Linux technically could, but the incentive to push for this is not nearly as high as the commercial incentives of providing this experience using Windows. So unfortunately it currently can’t.

    • Fubarberry@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      To be fair, the amount of tech support and help that low-skilled users need on windows would suggest this isn’t really true. A lot of these people have been using windows for decades and still have frequent issues with it.

      I’m not claiming that most Linux distros are better than windows with this, but I don’t think windows can be claimed to be a good OS for the tech-inept either.

  • Captain Aggravated@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    9 months ago

    At this point, that’s kinda the wrong question.

    I think Linux is just as if not more capable than Windows is, but the software library has some notable gaps in it. “It can’t run Adobe/Autodesk/Ubisoft” That’s not Linux’s fault, that’s Adobe/Autodesk/Ubisoft’s fault. I don’t think there’s a technical reason why they couldn’t release AutoCAD for Linux, for example.

  • leanleft@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 months ago

    drivers for lots of printers. no fuss gpu drivers. zero computer knowledge required.

  • DLSantini@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    9 months ago

    Run updates without me having to worry that “whoops, an update was fucked, and the system is not unbootable anymore. Enjoy the next 6 hours of begging on forums for someone to help you figure out what happened, before being told that the easiest solution is to just wipe your drive and do a fresh install, while you get berated by strangers for not having the entirety of the Linux kernel source code committed to memory.”

  • Piwix@lemm.ee
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Biometric login. It is available to an extent through fprint on Linux but support is not there for all hardware and it isn’t a very seamless experience to setup at the moment

    • verdigris@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      9 months ago

      Biometrics authentication seems to me to be entirely useless. It’s less secure and more easily spoofed than passwords, and if you need more security 2FA or a physical key (digital or otherwise) provide it. It would be nice to have the support I guess, but the tech itself just seems like a waste of money.

      • Coasting0942@reddthat.com
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        Setup right it’s a lot faster than passwords. So I guess it automatically wins vs more secure methods.

        I didn’t write the rules of average human thought processes.

  • xep@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Get some people to write really passionately about moving off of it, apparently.

  • TrickDacy@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    9 months ago

    Get credit for its strengths, mostly. That and play games with anti cheat bullshit.

    ITT: people confidently asserting that Linux can’t do things that it can do.

  • indigomirage@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Adobe lightroom (with its multi-device editing and catalogue management - even when only using its cloud for smart previews).

    Hardware support for music. NI Maschine is a non-starter. Most other devices are, at best, a ‘hope it works’ but are most definitely unsupported.

    Music software. You can hack your way into getting a lot of your paid modules to work, but it is certainly not supported.

    Wine is ‘fun’(?), but it’s a game of whack-a-mole chasing windows’ tail and will never allow everything to run. Either way it’s not 'supported.

    Businesses any any size tend to eschew SW/HW that doesn’t have formal support. (things like RHEL are most definitely supported as servers and orgs certainly leverage it).

    I keep installing Linux hoping I can get a sufficient amount stuff to work “well enough” to move on from windows but it’s just not to be (yet). Hope it changes, but it’ll require buy-in from commercial product developers. I hope as Linux continues to grow a foothold in desktop installs, a critical mass will be reached, commercial devs take notice and it’ll be easier to switch.

    For now, I’m stuck with Windows and WSL. (But I am not happy with Windows’ direction).

    • Paragone@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      9 months ago

      This commenter used “NI Maschine” as though everbody’d know what “NI” stood for…

      iirc, it stands for Native Instruments, and iirc, the “Maschine” is either hardware or hardware+software.


      The ONLY Linux distro which may do what theyre wanting, is UbuntuStudio.

      I happen to agree that it is a damn “whack-a-mole” “game” for us in Linux, and I"ve been experiencing that since 1996 ( when only Slackware mostly-worked ),

      but … if ever the spyware in MS’s products gets made illegal, then … Linux’d be the only lifeboat left?

      ( don’t tell me that Apple isn’t every-bit as much into privacy-molestation as the other Big Tech corpos are: they aren’t a real alternative )

      _ /\ _

        • Hexarei@programming.dev
          link
          fedilink
          arrow-up
          0
          ·
          9 months ago

          I beg you forgive my pedantic interjection, but … I posit that the original commenter is incorrect. it is absolutely native execution.

          The CPU is fetching and executing the instructions directly from memory, without any (additional) interpretation of code or emulation of missing instructions - Which is, by definition, native execution.

          What the compatibility layer “does” is provide a mapping of Windows system calls into the appropriate Linux system calls. Or, in other words, makes it so that calls to functions like CreateWindowEx() in the Win32 API have a (still native) execution path.

          The native execution requires you to install WINE, yes, but if we’re disqualifying it because “it requires you to install a package”, then we also consequently:

          • Add things like “print stuff”, “display graphical applications”, and “play audio” to the list of “things Linux can’t do”
          • Disqualifies Windows from “natively executing” any .NET applications (a Microsoft-built first-party framework), since .NET applications require you to install .NET.
          • JungleJim@sh.itjust.works
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            9 months ago

            You’re right, you are being pedantic.

            Edit: Actual response. You took time to type all that out, I should at least say why I disagree.

            WINE is a compatibility layer. A translator. It helps a non-native language speaker speak the native language. The whole reason WINE exists is to make a non-native executable execute outside of its native environment. Even if the code is very functionally similar to something like .NET, the function of WINE is to enable non-native code to run as though it were designed for Linux. Downloading WINE doesn’t suddenly make those .EXE files be retroactively designed with Linux in mind. It’s still not native code.

            • Hexarei@programming.dev
              link
              fedilink
              arrow-up
              1
              ·
              9 months ago

              You’re correct in that it is a compatibility layer - And I’m not disagreeing with that. Also to be clear: Not just arguing to argue or trying to start a fight, mind you. I just find this to be an interesting topic of discussion. If you don’t find it to be a fun thought experiment, feel free to shoo me away and I’ll apologize and leave it alone.

              That said, we appear to only be arguing semantics - Specifically around “native” having multiple contextual definitions:

              • I am using ‘native’ to mean “the instructions are executed directly by the CPU, rather than through interpretation or emulation” … which WINE definitely enables for Windows executables running on Linux. It’s the reason why Proton/DXVK enables gaming with largely equal (and sometimes faster) performance: There is no interception of execution, there is simply provision of API endpoints. Much like creating a symlink in a directory where something expects it to be: tricking it into thinking the thing(s) it needs are where it expects them to be.

              • However, you are using ‘native’ to mean “within the environment intended by the developer”, and if that’s the agreed definition then you’re correct.

              That’s where this becomes an interesting thought experiment to me. It hits me as a very subjective definition for “native”, since “within the intended environment” could mean a lot of things.

              • Is that just ‘within a system that provides an implementation of the Win32 API’? If so, WINE passes that test.
              • If I provide an older/fixed/patched version of a DLL (by just placing it in the same directory) to fix an issue caused by a breaking change to a program that is running on Windows, is that no longer native?
              • Or is it just ultimately that the machine must run the NT kernel, since that’s where the developer intended for it to run?

              Does that make sense? I hear a statement like that and I find myself wondering Which layer along the chain makes it “native”? - I find myself curious at what point the definition changes, in a “Ship of Theseus” kind of way.

              It seems to me that if we agree that the above means “running in WINE is not native”, then we must also agree that “anything written running for .NET (or any other framework, really) is not native”, since .NET apps are written for the .NET framework (Which is not only officially available for Windows, mind you) and often don’t include anything truly Windows-specific. Ultimately, both are providing natively-executed instructions that just translate API calls to the appropriate system calls under the hood.

              I hope that does a better job of characterizing what I meant.

  • oriond@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    1.- Make your computer slower and slower every year for no real reason. 2.- Get your files virus infected for not using an antivirus software. 3.- To be fair, get some really cool games.

  • Fizz@lemmy.nz
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Embed ads on your desktop.

    Play games with kernal level anti cheat

    Run professional software like fusion 360, Adobe suite and much more.

    Use Wsl to get a lot of the benefits of linux

    • xuniL@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      9 months ago

      Fusion 360 actually works under Linux with Bottles. Some other Autodesk products also have native Linux versions.

  • Surp@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    Windows is definitely easier to install older programs on. Linux is getting better, especially thanks to steam/valve imo, but it’s impossible to recommend Linux to just about anyone that’s not in IT or interested in tech as everything seems to have a caviat or workaround you have to do to get stuff either working or just limping along. For instance…I installed endeavor on my msi gaming laptop and getting it to use my 2070 card over my Intel graphics was a nightmare for a first timer. I can’t recommend it especially when I just wanna game.