Hacker News (curated)new | past | comments | ask | show | jobs| show hidden

And now a bunch of OSI-Approved licenses get to have special rules applied to them, entrenching them and killing further innovation.


The bill exempts:

> a person or entity that distributes an operating system or application under license terms that permit a recipient to copy, redistribute, and modify the software

which at least doesn't choose specific winners and losers among licenses. It does disfavor license-free and public domain software, which isn't great.


> It does disfavor license-free and public domain software, which isn't great.

Public domain software is free to "copy, redistribute, and modify", so ... where's the disfavour?


It only applies to software distributed under a license. Public domain software isn't distributed under a license. It's in the public domain; no license is needed.

Can you name an OS that's licensed as public domain?

https://www.pdos.org/ Public Domain Operating System

TempleOS

Technically you could argue that public domain works don't have license terms that make them free so the exception can't apply. Only an ignorant or ultra literalist judge would see it that way but you never know.

On the other hand a public domain dedication is a binding term that gives you permission (or license) to do what you want...


Sure, but of minimal practical impact. The Free and Open Source community has long discouraged releasing software into the public domain, as it has clear drawbacks compared to just using a permissive licence. The legal intricacies of the public domain vary between jurisdictions. Not all jurisdictions even allow copyrights to be surrendered in this way. [0]

Licence-free isn't a concern. That isn't even close to Free and Open source software, it's the opposite: software that you aren't permitted to acquire, use, modify, or distribute. [1][2]

[0] https://opensource.org/blog/public-domain-is-not-open-source

[1] https://choosealicense.com/no-permission/

[2] https://docs.github.com/en/repositories/managing-your-reposi...


This is exactly what GP was talking about: entrenching a preference for one style of licensing over another. We all know what set of licenses the FOSS zealots would prefer for us to release code under, and those who release license-free or public domain software anyway typically do it with full knowledge of such arguments.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact | github