TLDR: Companies should be required to pay developers for any open source software they use.

He imagines a simple yearly compliance process that gets companies all the rights they need to use Post-Open software. And they’d fund developers who would be encouraged to write software that’s usable by the common person, as opposed to technical experts.

It’s an interesting concept, but I don’t really see any feasible means to get this to kick off.

What are your thoughts on it?

  • BaumGeist@lemmy.ml
    link
    fedilink
    arrow-up
    19
    ·
    edit-2
    11 months ago

    people are always going to be floating ways to save capitalism in the face of communities privileging freedom over greed.

    this completely misses the point of free software, and fails to solve the problems Mr. Perens identifies with Open Source. He claims it fails to serve the “common person” (end users) and then proposes a solution that serves… only devs.

    Open Source has completely failed to serve the common person. For the most part, if they use us at all they do so through a proprietary software company’s systems, like Apple iOS or Google Android, both of which use Open Source for infrastructure but the apps are mostly proprietary… Indeed, Open Source is used today to surveil and even oppress them.

    All these problems are already solved by free software. the rebranding of “open source” was a compromise on the principles of free software to make the movement palatable to profit-seekers. In the end, it predictably failed to improve anything. The solution isn’t to reinvent the wheel, it’s to stop making the wheel square because the square lobby insists they’ll only use it if it’s square. The solution is copyleft, and free software being used more than it’s defanged cousin.

    The common person doesn’t know about Open Source, they don’t know about the freedoms we promote which are increasingly in their interest

    That’s a feature, not a bug. On one hand, if people knew about free software they wouldn’t be as good consumers. On the other hand, internals should be opaque to users; just as devs don’t want to have to know how the logic gates in the CPU are routing their code to write code, end users shouldn’t have to worry about the politics of the communities that developed their code.