• Nate Cox@programming.dev
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    14 days ago

    Or, we could choose not to use slopware. Especially when they appear to mostly be wrappers around software we can configure ourselves.

    It’s hard to responsibly use tech built irresponsibly.

    • tatterdemalion@programming.dev
      link
      fedilink
      arrow-up
      1
      arrow-down
      2
      ·
      12 days ago

      How do you know it was built irresponsibly without reading the code, which is something you should be doing when adopting a dependency anyway?

      • Nate Cox@programming.dev
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 days ago

        See: data centers, noise and cooling.

        See also: intellectual property, theft of; infringement, copyright.

        • tatterdemalion@programming.dev
          link
          fedilink
          arrow-up
          1
          arrow-down
          3
          ·
          11 days ago

          You don’t know the direct impact of this project on data center usage because you haven’t observed the development process. And you don’t know whether it infringes on copyright because you haven’t read the code.