From: Akira Urushibata <afu@wta.att.ne.jp>
To: <libreplanet-discuss@libreplanet.org>
Subject: GPL on AI generated code
Date: Thu, 16 Feb 2023 06:17:13 +0900 (JST) [thread overview]
Message-ID: <2023.02.16.06.17.13.131492001@afu.wta.att.ne.jp> (raw)
I recently read that Chat-GPT is capable of writing computer code.
Can ChatGPT Code? [With Examples] - Legiit Blog
https://legiit.com/blog/chat-gpt-code
Chat GPT Code can help you do all sorts of things, from writing
code to solving complex calculations. Here are a few of the
cool things you can do with Chat GPT Code:
1. Write Code for Different Languages - As mentioned earlier,
Chat GPT Code currently supports Python, JavaScript and HTML,
but it plans to add other languages soon.
2. Debug Code - One user found that ChatGPT Code was an
excellent debugging assistant as it allowed him to explain and
fix a bug quickly.
3. Develop Games - You can use Chat GPT Code to develop a game,
which is an exciting and fun way to explore the capabilities of
this chatbot.
4. Solve Complex Calculations - ChatGPT can be used to solve
complex calculations and equations. Just provide the correct
commands and parameters, and Chat GPT Code will provide you
with an accurate solution in a matter of seconds!
...
---
As I understand Chat-GPT does not compose code the way most
programmers do. Rather it looks for code within its memory which
appear to fit the descriptions of what the user is requesting and
produces an answer. This looks like an inductive, as opposed to a
deductive, process.
I have a question. If the reference material is GPL'd code, shouldn't
the code produced by AI be considered a modified version? Human beings
are free to modify GPL'd source code and distribute the result,
provided that the GPL is attached. Is there some reason the same
restriction would not apply when a machine does the modification?
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next reply other threads:[~2023-02-16 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 21:17 Akira Urushibata [this message]
2023-02-16 16:06 ` GPL on AI generated code Paul Sutton via libreplanet-discuss
2023-02-19 0:06 ` Akira Urushibata
2023-02-21 2:05 ` Marc Sunet
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 22:55 Akira Urushibata
2023-08-15 16:33 ` Runxi Yu via libreplanet-discuss
2023-08-16 3:41 ` Alexandre Oliva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023.02.16.06.17.13.131492001@afu.wta.att.ne.jp \
--to=afu@wta.att.ne.jp \
--cc=libreplanet-discuss@libreplanet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).