Lately I often read about kbin.social being similar to lemmy but more accessible. So I created an account there to check it out. My experience so far is a little mixed. From kbin I can access all Lemmy posts, although I find the interface less intuitive to join new communities. So from the kbin side it feels like an other Lemmy instance.

But when searching for kbin from this Lemmy Account, I do not find much. I feel like I am missing some basic concept, that makes it pretty clear. Why this is such a one way experience.

So now I am wondering: How does this work, what are the difference, what do both sites have in common?

  • damn@lemmy.fmhy.ml
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    2 years ago

    I’m sure it’s fine code, I just can’t imagine it’ll ever be as efficient as Rust.

    • ccunix@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 years ago

      If it can run on PHP8 you get JIT compilation, which should go a long way to closing any gaps (if they exist, which I suspect not).

    • poVoq@slrpnk.net
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      2 years ago

      Lemmy is not bottlenecked by anything related to the Rust code and neither is Kbin most likely. Modern php is efficient enough for it to not really matter (contrary to Python or Ruby etc.).

      • taladar@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        2 years ago

        Modern PHP is better than PHP5 but it still uses that brain dead execution model where every request starts the entire framework from scratch.

        • i_suppose@feddit.it
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 years ago

          actually that model is now optional thanks to some PHP extensions which can bypass the bootstrap and keep everything running. But it’s not something that is always needed, since the share nothing architecture works fine for most use cases