• flamingos-cant (hopepunk arc)@feddit.uk
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 months ago

        So? It’s logname, what do you expect, for them to read the bits directly from memory? If you’re going to criticise this for anything, it should be that it doesn’t support Windows, not that it calls out to libc.

        • four@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          I no longer use any wrappers or utils, they’re just bloat. Now I just use my dousing rod to read and set bits in my RAM, way more efficient

  • Eggymatrix@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    I mean, have you ever looked at any low level code from any language that came out in the last 30 years? Its always C.

    • cockmushroom@reddthat.comOP
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      Sure, but they don’t usually have the audacity to market themselves as a viable alternative and cannibalize its system interfaces (or, in this case, claim to)

      • Eggymatrix@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        3 months ago

        Good engeneering solutions are better than steering clear of hypocrisy. The rust zealots will happily tell you that this is just an implementation detail, YOU should write rust, because you will have no bugs, they instead need to ship, so concessions need to be made.

  • stingpie@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    I’m not that well versed in rust, is this literally just wrapping the C library in rust, and calling it a rust implementation of it?