Sure, I was merely thinking out loud (bad move it seems from the children comments) how to solve the "need billions, got maybe millions" issue, and since I can't get stable diffusion out of my mind, as everyone recently, I just saw it as a possible light at the end of the tunnel: why not let the machine implement the specification.
I am all for going back at the roots, but at the root of all the roots is the enduser: the machine must do something useful, otherwise it's a niche postmodernist art contraption (not that there's anything wrong with that).
I think the "if-else nightmare logic" caused some non-friendly answers over there but I get your idea.
I don't entirely agree with the end user being the root of all, at least in FOSS. While they shouldn't be alienated, the focus should be on having a good approach to the project, one that is friendly with the idea of having to code after a full time job, like most open source developers do.
Keep in mind that this isn't a job, nobody will fire you and most complains by end users can be ignored with no consequences. If the project is not fun and engaging, then what's the incentive to keep going?
My point was that a machine is always intended to make some useful work, and even as a sole developer of a private project, that project still has one enduser, the developer itself, since the existence of the project is to achieve meaningful computation one way or another, even if that computation is performed only in the test suite, hence the enduser as root. However, as a project organizer, sure, you want to strive for welcoming others, making it easy to embark, 1-cli command to setup, interesting to engage and persevere in development, and so forth.
I am all for going back at the roots, but at the root of all the roots is the enduser: the machine must do something useful, otherwise it's a niche postmodernist art contraption (not that there's anything wrong with that).