This popped up on my work laptop yesterday. Very annoying.

  • Cosmic Cleric@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    edit-2
    2 years ago

    How is that ironic?

    The irony is having to use one kind of licensed tool on another diametrically opposed type of licensed tool.

    Its not how the tool is used (as you described), but the licensing of the tool, versus the licensing of the tool its being used on.

    That seems self-evident, considering I went out of my way to express the licensing in my original comment. But, if you have a better word for me to use than ironic, please let me know.

      • Cosmic Cleric@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        3
        ·
        edit-2
        2 years ago

        I guess if you think it’s ironic then you do you.

        You honestly see no irony, license-wise, in using an open source product to repair/modify a closed source product?

        At all?

        I’ve been using OSS software to make proprietary OSes not suck for almost 3 decades, and that’s exactly one of the things I expect it to do.

        No one is disputing that. That’s not the point being made.

        But, if you have a better word for me to use than ironic, please let me know.

          • Cosmic Cleric@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            2
            ·
            edit-2
            2 years ago

            Again, it’s not how the tool is used, or what the tools used on, it’s the licensing difference, that is the irony.

            That closed source products have to rely on open source products, to be modified to work well.