9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] Invitation for testing a new game for 9front: Jetpack Game
Date: Sat, 22 Jul 2023 17:13:50 +0200	[thread overview]
Message-ID: <6A18535D2E91EC21922F41C918A8222C@wopr.sciops.net> (raw)
In-Reply-To: <026861bc-64bb-aafb-5613-0510420f8d35@posixcafe.org>

On Sat Jul 22 16:14:36 +0200 2023, moody@mail.posixcafe.org wrote:
> On 7/22/23 08:31, Csepp wrote:
> > https://limited.systems/articles/climate-cost-of-ai-revolution/
> 
> Indeed, there are also unanswered questions regarding the legal
> owner of intellectual property of code like this. It is impossible
> for us to verify that this code is respecting the license of the
> code that influenced it.
> 
> As the kids say:
> "this is a no from me chief"
> 
> Thanks,
> Moody

It doesn't work anyway.  It has multiple bugs, and makes several
bizarre choices that don't make any sense.  It literally has output
typical "I have no idea what I'm doing" copypasta.  Event code might
be common enough that it copies the overall structure in a sort of
plausible way, but it gets wrong anything more technical such as
timing and blocking i/o.  It doesn't quite follow style(6) either.
Chatgpt's entire goal is to output plausible looking answers, not
exact or correct.  Therefore I think that this is a pointless
exercise; you cannot trust it and must review and correct all of its
mistakes anyway.  If you want to learn to program 9front software, do
that instead of trusting some language model.  My 2¢.

Cheers,
qwx

  reply	other threads:[~2023-07-22 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 22:24 PeacefulGena
2023-07-22 13:31 ` Csepp
2023-07-22 14:10   ` Jacob Moody
2023-07-22 15:13     ` qwx [this message]
2023-07-22 21:01       ` PeacefulGena
2023-07-22 21:21         ` qwx
2023-07-22 16:28 ` ori

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6A18535D2E91EC21922F41C918A8222C@wopr.sciops.net \
    --to=qwx@sciops.net \
    --cc=9front@9front.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 NNTP newsgroup(s).