• stormeuh@lemmy.worldEnglish
      0·
      4 months ago

      IMO this should be the case for everything developed using public money, looking at you, pharmaceutical companies…

      • Liz@midwest.socialEnglish
        0·
        4 months ago

        The issue becomes when things are developed with a mix of public and private money. I’m not saying we shouldn’t tackle the issue, only that it can’t be as simple as public money = public resource. If that were true, nearly all of us would be required to work for free, since we got the majority of our education through public funding.

        • logging_strict@lemmy.mlEnglish
          0·
          4 months ago

          govts print infinite money. All of us are working for free. Their fiat is credits for the company store.

          If you think funding projects is bad then the response is to support lobbying project owners to put in malware until FOSS is publically funded.

          All we have to do is verbally support it. And cheerlead when it occurs. We don’t actually have to actively do it. It’s a threat which is done in politics all the time.

        • MonkderDritte@feddit.deEnglish
          0·
          4 months ago

          There’s the difference between individual knowledge (company training) and code licenses though.

        • nfh@lemmy.worldEnglish
          0·
          4 months ago

          I don’t think anyone intends public funds to be quite that sticky; public education is itself a public good, and having once attended a public school really has nothing to do with developing a product 20 years down the road.

          Also, writing open source code can support a viable business. Not every example has been successful, and some have been sold to hypercapitalist owners who wanted to extract more profit, others have failed to keep up, but Canonical is doing alright with it, Red Hat did for a long time, among others. Plenty of bigger tech companies also employ people to write open source software, despite it not being the company’s main business, React, PyTorch, TensorFlow, and so many other projects. Those engineers definitely aren’t working for free.

        • ipkpjersi@lemmy.mlEnglish
          0·
          4 months ago

          You can still pay people to write public code, though. Just because you can use it for free doesn’t mean it always has to be written for free. In some cases, sure, it can make more sense to have it for free if it’s a fully non-profit volunteer-run project, but that is not the only way to write open-source software. Talented developers are still talented, open-source or not.

    • Tja@programming.devEnglish
      0·
      4 months ago

      But it will be written in Schwiizerdütch, so no one outside of Switzerland will understand it. I think it’s a dialect of Perl.

      • Onno (VK6FLAB)@lemmy.radioEnglish
        0·
        4 months ago

        Your joke aside, which I thought was funny did remind me that as it happens, the Swiss do an amazing job in making things internationally accessible.

        Take for example their spectrum management system that not only allows you to search for categories of users, handles kHz to MHz data entry, gives access to the legal provisions and then the legislation itself, does so in four languages.

        https://www.ofcomnet.ch/#/fatTable