The page The Javascript Trap describes guidelines for making JS code free/libre. I know that this is considered mandatory in web pages, but do the same rules apply to server-side JS? For example, do I need to add license comments in my Node or Deno scripts? If so, is there something like LibreJS for the server-side?
4
-
If you're running JS server-side, then you will know where it comes from and should know what its license is. So I don't really understand your question.– curiousdanniiCommented Jun 6, 2020 at 14:17
-
@curiousdannii I think this question asks about voluntary compliance with the FSF's annotation guidelines for JavaScript, for the benefit of users of one's web service. It doesn't matter that the operator of the service knows this information, since the substance of the question is how/whether to communicate with information via annotation (i.e., the "method by which a nontrivial JavaScript program in a web page can state ..." in the linked article)– apsillers ♦Commented Jun 6, 2020 at 14:31
-
@Apsillers Right, but server-side JS isn't really a "web page" in any sense.– curiousdanniiCommented Jun 6, 2020 at 14:56
-
@curiousdannii I think that's more or less the answer to this question: the guidelines being linked to are not applicable to the server-side case in question, so there do not exist annotation guidelines for this case.– apsillers ♦Commented Jun 6, 2020 at 14:58
Add a comment
|
1 Answer
In a word: no.
The FSF advocates for LibreJS annotations because of the special place web browser scripting plays in the lives of web users. The linga franca for browser scripting happens to be JavaScript.
Server-side code gets its own consideration from the FSF but the use of JavaScript as a server-side language does not merit more consideration than any other language. In other words, if you have a service written in JavaScript and you rewrote it in another language, the FSF's recommendations pertaining to those two implementations would be identical.
answered Jun 6, 2020 at 20:08
