we're tired of hearing "it's just a tool" because, well, a) we disagree and

b) let's pretend that we agree. okay, it's a tool: who made it? why did they make it? what is this tool good at doing? is it any better at doing it than the previous methods by which we would do this thing? why should i use it for that? can you demonstrate the tool's utility in a situation i propose? are the tradeoffs worth the benefits? can you answer *any* of these questions?

but no, people just say "it's just a tool" and it's inevitable and we just have to get used to it, no questioning allowed, no objections allowed (see also: the cries of discrimination coming from adafruit) , and the conversation stops there. weird, huh.

@atax1a
It can be a tool when the user of the tool can verify the result. Not all tools are of equal quality. My experience producing a really quite Micky Mouse app (for instance) using CrapGPT, it generated badly written code, which at least worked. However, it hallucinated constantly in development saying โ€œThis will workโ€, remaining unrepentant in the face of syntax and run time errors; even blaming me. Sadly when the app needed a tweak I was abruptly hung by my own petard.
@H4Heights i think the tool here was you