cross-posted from: https://beehaw.org/post/570507

After the (temporary) defederation announcement of earlier i checked the Lemmy repo to see if there was already a ticket on the federation limiting option like Mastodonā€™s that people mentioned Lemmy doesnā€™t yet have. Not only i didnā€™t find it, i also saw that thereā€™s about 200+ open tickets of variable importance. Also saw that itā€™s maintained mostly by the two main devs, the difference in commits between them and even the next contributors is vast. This is normal and in other circumstances itā€™d grow organically, but considering the huge influx of users lately, which will likely take months to slow down, they just donā€™t have the same time to invest on this, and many things risk being neglected. Iā€™m a sysadmin, havenā€™t coded anything big in at least a decade and a half beyond small helper scripts in Bash or Python, and havenā€™t ever touched Rust, so canā€™t help there, but maybe some of you Rust aficionados can give some time to help essentially all of Lemmy. The same can be said of Kbin of course, although thatā€™s PHP, and there is exacerbated by it being just the single dev.

  • barsoap@lemm.ee
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    7
    Ā·
    edit-2
    1 year ago

    Oh my sweet summer child :)

    Remember that borrowck is not out to hurt you, it wants to help you, guide you towards enlightenment, and does so with grandfatherly kindness: Making you feel completely stupid.

    If you hit a wall make sure to check out the Rust book and work through it, or at least read it: Unless your language background is very specific (letā€™s see C/Pascal or such, plus Haskell, plus very obscure research-grade ML dialects with region-based memory management) Rust semantics are going to kick your ass sooner or later.

      • barsoap@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        3
        Ā·
        1 year ago

        Can we stop tone-policing friendly heads-up? Itā€™s all a long-winded recommendation and reminder to go back to the Rust book if (or rather when) you get stuck.

        Even Bryan Cantrill ended up reading through the book, going step by step. Thereā€™s no shame to it.

        • derivator@feddit.de
          link
          fedilink
          English
          arrow-up
          5
          Ā·
          1 year ago

          I donā€™t find ā€œOh my sweet summer child :)ā€ all that friendly, I find it condescending and weird. Recommending the Rust book I have no issue with.

          • barsoap@lemm.ee
            link
            fedilink
            English
            arrow-up
            3
            arrow-down
            1
            Ā·
            1 year ago

            It means as much as ā€œYou have not yet experienced the hardships I have, and therefore have an idealistic view of thingsā€.

            As to weird well yes itā€™s a Game of Thrones reference.

    • ehrenschwan@feddit.de
      link
      fedilink
      English
      arrow-up
      5
      Ā·
      1 year ago

      I just started writing more rust code. And until now the borrowck only has been useful. The suggestions inside of the lsp feel like magic. Other lsps only scream at you when youā€™ve done something wrong. The rust lsp tells you how to do it right. And sometimes with such a high level of understanding of what Iā€™ve written, it almost feels like a pair programmer.

      • barsoap@lemm.ee
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        Ā·
        1 year ago

        Things definitely got better with non-lexical lifetimes, yes, and that might be the reason that we donā€™t see that many complaints about it, any more.

        ā€¦but not because it wonā€™t at some point be an obstinate bridge troll pointing you in exactly the wrong direction actively hindering you from figuring out what you did wrong (without understanding the underlying semantics), but because people actually had positive interactions with it before, thus not immediately judging it all bad. But itā€™s going to get you, too, just wait for it. Itā€™s looming, lurking, in the depths of the compiler, ready to strike when you least suspect :)