It’s not easy to build a good tui though. Like fe compare Claude code and opencode. Opencode is an atrocious approximation of a window system as a tui.
AFAIK it has enough precedent (also depending a bit on jurisdiction, but you only need one) but the interpretations of what that/the license should cover differ. Like f e if you wanted to argue driver devs would have to open-source their firmware blobs or their proprietary driver loaded by a kernel shim you will have a tough time and prob lose
Under any current / capitalist system by design it won’t be different because managers/capital want to increase gains, which contradicts allowing you to keep the gains.
it's telling that he only sees effectiveness in what he wants. these rules are there for environmental protection, and in a worst case scenario, a fine is not gonna bring back the clean soil, or whatever was done.
The immediate no for scientific collaborations is zotero support being paid only. If it was just one user, sure they could decide to pay. But no way I am convincing others to sign up. (If this is somehow possible without paying while not ‚syncing‘ it’s not obvious)
If the project owner has paid for pro, all collaborators can use the pro features in the project.
Zotero sync is just a .bib file that updates itself regularly, so if you don't want to pay, you have to upload the .bib file or past the new entries manually.
reply