Recently joined and started a community for people who want to move away from Lemmy and want to see Lemmy loosen its stranglehold on the threadiverse, if that seems like something interesting to you consider checking out !cancel_lemmy@piefed.social

  • Draconic NEO@lemmy.world
    link
    fedilink
    English
    arrow-up
    21
    arrow-down
    4
    ·
    3 days ago

    I’ve always thought it was really weird and really dumb sentiment to want to cancel Lemmy, as an Open source software. It’s like people think they need to endorse the developers’ views to use Lemmy, or pay them money to use the software. But like that’s really dumb. Lemmy is free and opensource software, the developers have no say in who uses it, it’s also opensource meaning anyone can fork it. So this position just seems weird and reactionary.

    One thing that really makes me reluctant about the future of piefed is the fact that it runs on Python. Great for tinkering but it likely won’t scale well, and Python is famous for breaking backwards compatibility. So expect this project to be hosed when Python 4 or 5 comes out and breaks compatibility or syntax with the previous version. I saw this happen with Kodi and other platforms with Python Based plugins, and it’ll most definitely happen again, not to say it can’t happen with something like Rust or Go, but these compiled languages are designed for big projects, python is just one-off scripts, so the ones maintaining languages like Rust, Go, C++ work a bit harder to keep them as functionally compatible as possible so big projects aren’t crippled and trashed by an update.

    Anyway that’s my opinion on this whole thing, I don’t believe Piefed is the future, and I do not think Instance Admins should jump at the chance to abandon Lemmy. Maybe for sublinks if it ever comes out, but not for piefed.

    • db0@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      1
      ·
      3 days ago

      Mate,you have a 20 year old perception of python. “good for tinkering”, Cheezus…

      • Draconic NEO@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        3
        ·
        edit-2
        3 days ago

        Are you denying the problem of Backwards compatibility with python versions? It was and still is a big problem today. I’m still seeing the affects of that though many communities. I don’t really think it’s only good for tinkering but I know its developers clearly do, otherwise they wouldn’t have subjected us to the transition from python 2.7 to python 3 and the fallout that followed, and people wouldn’t have been so eager to comply with them dropping python 2.7 support in all their python integrated envionments before you could say bitrot.

        Yeah somehow that doesn’t give me much confidence for the future.

        • db0@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          10
          arrow-down
          1
          ·
          3 days ago

          Python 2 transition took decades and EOL was almost a decade ago, get over it. If you still want to use it, use it!

          I don’t understand this approach at all. Software evolves and sometimes you need breaking changes. Godot did it as well, but I guess that “great for tinkering” as well.

          It fills me with confidence that the language is the most widely used in the world and is not afraid to do what must be done instead of growing stale and unwieldly so that lazy developers don’t learn anything new.

          • Draconic NEO@lemmy.world
            link
            fedilink
            English
            arrow-up
            4
            arrow-down
            1
            ·
            3 days ago

            Yes I don’t think that demolishing whole ecosystems is a good thing. I think that it’s a shitty mentality of wanting shiny and new shit and fixing what isn’t broken. I am a believer in legacy support and I find it weird and concerning to see and hear people complain about it. You do realize that if Python had been the Web’s scripting engine instead of JS, a lot of Websites would’ve been, and still would be trashed and unusable due to said breaking changes with zero regard for legacy support. Thankfully that wasn’t the case, but it does go to show that legacy support and backwards compatibility is important.

            • db0@lemmy.dbzer0.com
              link
              fedilink
              English
              arrow-up
              7
              arrow-down
              1
              ·
              3 days ago

              Again, python 2 still exists. nothing would be “trashed”. If you want backwards compatibility just keep using python2. We clearly don’t see things the same way, but given that python is the most popular languge in the world, I’m happy most see it my way.