3 ms·
The standard library is owned by the people creating it, and of course your work using the standard library is a derived work of that standard library. For exa
by tsimionescu 6y ago
The standard library is owned by the people creating it, and of course your work using the standard library is a derived work of that standard library.
For example, glibc is owned by GNU, and it is licensed under the LGPL, so you are allowed to dynamically link it without having to release your own code under the GPL (or compatible). This is all happening today.
The only projects that will be more seriously affected by this decision are WINE and similar - projects that are copying the API but not the implementation. Even here, it is very likely that WINE could win on Fair Use, since their copying is obviously done for interoperability.
Also, APIs are obviously creative human works, and their purpose is first and foremost usability for the end-user.
- diminish 6y agoMaking a drop-in replacement for interoperability for any library or API could fall victim under the current law.
- joshuamorton 6y agoBut now if I write my own libc implementation, someone (who?) could come after me for violating their copyright on the libc api.
- tsimionescu 6y ago> who? That's an interesting question. Perhaps K&R? Or maybe their employer? Or perhaps by now the copyright may be with ANSI/ISO? But this does raise an interesting point, about who would own copyright on something that was not believed to be copyrightable for much of its history.
- lern_too_spel 6y agoThe C standard library's API would belong to AT&T. Same with Unix syscalls. Glibc would be infringing.