I’m here because it’s eventually going to be the better alternative.

FOSS by its nature, will keep on improving. And proprietary bloatware, by its nature, will only gonna get worse.

  • Aurix@lemmynsfw.com
    1·
    1 year ago

    I would not agree with the general statement about FOSS. Some commercial products absolutely do edge out the free ones. And I am not sure it is only the limited funding, seeing the usability issues with Linux. I think Linus Tech Tips video series was a nice insight.

    But for social platforms I do not even see a different way. FOSS is a must, especially with the inherent bias of algorithms. Commercial third party clients still could be beneficial.

    • ChosenUndead15@lemmy.world
      3·
      1 year ago

      About Linux, I feel Con Kolivas, a former Linux kernel dev said is very accurate. There could be a bug in the kernel that causes desktop use case go to a crawl or freeze can be ignored for years, but Oracle reports there is a bug in the server usecase that causes a 0.5% of performance lost once per month and the same day it will be fixed.

      Enterprise use simply eclipse the focus of the devs to regular people use. Which just only highlights even more why the desktop experience improved so rapidly when Valve decided they wanted Linux for gaming. Simply there wasn’t anyone that cared for the end user experience and wasn’t running their own fork (yes, I am talking about Google).

    • Zetta@mander.xyz
      1·
      1 year ago

      I think Linux usability is very good. The problem is the vast majority of Linux distros aren’t great.

      I switched to Fedora from windows a year or two ago, I’ll never look back.

      • venuswasaflytrap@lemmy.ca
        1·
        1 year ago

        This sort of thing is quite different technically.

        With Inkscape, blender and gimp - the main draw is an extremely complicated UI that produces image files. A social network is just sending text around back and forth.

        The beauty here is the activitypub spec. The way it works is like:

        ActivityPub Protocol <- Lemmy Backend <- Lemmy Client

        Building a replacement backend or client is comparatively trivial. Making a good one would be hard, of course, but a single developer could whip up something that’s technically a lemmy client, or technically a activitypub backend over a weekend.

        That decoupled layering, the idea that each bit just does one comparatively simple thing, is intentional.

        If lemmy/kbin catch on (which it looks like they are), it will be not long at all before there are a a plethora of tools and clients cross platform.