Are programming language names copyrighted? Say I want to create a programming language with some name, but there already exists another programming language with the same name. Could I get in trouble (legal or otherwise) if I create another programming language with this same name?
It would not be a copyright. Names and short phrases are not subject to copyright, but it could be a trademark under common law ( e.g. state law in the U.S.) or could be registered. Some people think a trademark defines a product. That is not the case, a trademark identifies the source of a product or service.
If users were to copy dictionary definitions, for instance Oxford or Cambridge) and make the word lists public, is it a copyright infringement? If the dictionary entries are protected by copyright then your user has infringed that copyright by posting the dictionary entries. Am I responsible for this activity? No. But you may be responsible for removing it if you get a request. Can dictionary owners charge me against copyright issue? If you follow the procedures outlines in the DMCA you can be protected from liability.
First off: Legally, everything is copyrighted anyway. Licensing is not at all necessary. Hence, even if a court would disagree with # SPDX-License-Identifier: Apache-2.0, that would just make it closed source. Having said that, the law generally doesn't bother with trivialities such as &quot;file headers&quot;. Any commonly accepted way to state the copyright and license terms is OK. Your LICENSE is such a common convention. If you want to avoid all doubt what is covered under that license, put a reference to that LICENSE in each header. If you have just five files in one directory that are all licensed the same, I wouldn't even bother with that. Again, the default position is that everything is closed source.
If the code is unrelated to your employment you own the copyright no matter if it is written in Visual Studio, on a piece of paper or tattooed on your butt. In the same way a sculptor owns the copyright in their sculpture even if they use someone else's chisel. Using Visual Studio in this way may, however, violated your contract with your employer and/or their contract with Microsoft. Why go there? Visual Studio Community is free.
Hypothetically speaking, if a program doesn't come with a EULA, does that mean someone in possession of it (who isn't the owner) would be breaking the law if they used it? If the copy on the stick was lawfully made with permission of the copyright holder, then you can lawfully use the software. Someone who lawfully comes into possession of a lawfully made copy of the software (that was not a backup) has the right to use that software in the ordinary way. For example if someone found a USB stick lying on the ground and it had software on it but no EULA, could they use the software? Maybe, but it would be hard for them to know whether they could or not. It might be a backup. It might be an unlawful copy. There was a case where a person found a CD in the trash that was clearly an original. The package had a shrink wrap agreement, but he found the CD without the package. The court held that he had every right to use the software on the CD (since it was a lawfully-made copy and not a backup) and was not bound by the EULA (since he hadn't opened the package). But he was very fortunate in being able to demonstrate these facts.
If you are subcontracted, then some other company is going to use the code that you wrote, and since you were not paid for it, you are the copyright holder. A letter to that company's legal department might work wonders.
Exactly the same way it works over all other content There are no special classes of copyright, there’s just copyright. What a user of a service may do with copyright materials will be spelled out in the licence. If there is no licence, then they are left with fair use/fair dealing.
You are in general correct, KBurchfiel. A code snippet such as import math; or For i := 1 to 10 print i; has no originality, and is not protected by copyright. A post eplaining the meaning an usage of such a snippet might well be original enough to be protected by US copyright, indeed it probably would. But the code on its own would not be. Anyone could read such a post, and if s/he understood it, use the code snippet and not be in violation of copyright, not compelled to place the entire program in which such a snippet was used under a CC-=BY-SA license. The creative commons people would prefer that a CC license not be applied to a publication that is not protected by copyright, and if it is so applied it is legally meaningless. But they have no legal way to enforce such a preference. A stack exchange post that consisted of nothing but such an uncopyrightable code snippet, with no explanation r discussion, might well be downvoted or even deleted. But that is a matter of site policy on what is a useful answer, not a matter of copyright. Using an excerpt from a copyrighted work so small that the excerpt alone would be uncopyrightable, would probably be fair use under US law, and might well be fair dealing in UK law. Something that is fair use does not compel the reuser to abide by the terms of a CC license, because those terms apply only when the content could not be reused without the CC license's permission. However, a code snippet does not need to be very much more original than the above examples before it becomes copyrightable. Whether it can be used via fair use rather than via the CC-BY-SA license is a very fact-based decision (the usual four-factor analysis is spelled out in 17 USC 107).. But if the snippet can be rewritten to express the same concepts but in a different expression, then there is no copyright issue, and again the CC license will not apply. If the snippet is complex and original enough to be copyrightable (a fairly low bar) and it is re-used unchanged, under conditions where fair use does not apply, then the CC-BY-SA license's terms must be complied with for the use to be legal. That is several &quot;IFs&quot; however. The exact details of a specific case will matter in such cases, there is not one rule for all snippets, all posts, or all programs.