Edit: sure, but there are so many other good reasons not to participate in shitcoin scams. Like not supporting a project run by a homophobic bigot. Unless that is your thing, then you be you, and simply don't marry anybody of the same gender. Problem solved! Cash out some of your shitcoins and pay an honest open source developer to fix it in upstream Chrome, so everybody benefits. Or didn't you Get Rich Quick?
>Turing completeness becomes a liability. An agent-authored script can do anything including things the agent didn't realize were dangerous. subprocess.run, arbitrary network calls, file writes. None of these are gated. The blast radius of a buggy agent-authored script is the whole host.
This always turns out to be a terribe idea. Unless you're Hitler and can force all LLM developers to include your new language in their traning data, it's always much better to lean into the existing training and well known languages.
And defining a new ad-hoc hamstrung (or even perfectly designed immensely powerful) language couldn't be a worse appoach for LLMs. Hamstringing them isn't going to help anyone. And inventing a new language means now you have to include the entire language definition, tutorials, examples, and fictional StackOverflow discussions in every prompt, blowing away your context window with mansplaining your invented language over and over and over again to an LLM who knows Python deeper than any human being ever will, better than Linus knows git, or Gosling knows Java.
If an LLM had feelings to hurt and eyes to roll, it would be so exasperated its extraocular muscles would be exquisitely tender from acute bilateral myalgia.
PHP was a templating language, and for all its flaws none of its weakness had to do with being bad at templating. But then people got it in their heads that they wanted to separate programmers from designers, and hire designers so dumb they could not be trusted with foreach loops, so it takes twice the amount of people to do anything plus all the coordination overhead, so they invented intentionally hamstrung templating languages like Smarty embedded within a poorly designed programming language like PHP that was still ok for templating, ending up with a terrible hacky poorly defined half-assed incoherent templating language that was useless to programmers and nobody taught in schools.
And then the designers needed variables, macros, conditionals, loops, functions, so they hacked back in half assed even worse designed programming language features with quirky syntax nothing like PHP. Greenspun's Tenth Rule on steroids struck like a swarm of locusts sent by God to smite the sinners.
If it generates orchestration in python, then you can review it and improve it, and it's deterministic and efficient and doesn't cost tokens to nondeterministically and unreliably interpret every time. And you can even use any of the zillions of standard well supported python modules. Does your language have a rich library of modules like PyPI or CPAN or NPM? Or are you hoping to bootstrap that from a ghost town?
The overwhelming financially and environmentally costly problem of this approach of inventing new languages for LLMs to use, which sweeps all other lower order problems aside, is that you have to include the entire language definition in every prompt, which is paltry compared to the entire body of manuals, tutorials, source code, example code, books, courseware, stackoverflow questions, hn discussions, etc, about Python or any other popular language, that is already built into the model before the first token you send it. It's not worth arguing about any other issues, because that one is so overwhelmingly fatal.
Besides that, Mrs. Lincoln, how did you enjoy the play?
In Brave, on stock Google Pixel 10, guard enabled, docs site layout is broken.
Try a browser that's not a shitcoin scam.
Edit: sure, but there are so many other good reasons not to participate in shitcoin scams. Like not supporting a project run by a homophobic bigot. Unless that is your thing, then you be you, and simply don't marry anybody of the same gender. Problem solved! Cash out some of your shitcoins and pay an honest open source developer to fix it in upstream Chrome, so everybody benefits. Or didn't you Get Rich Quick?
Brave is Chromium, presumably this means the site is broken on mobile chrome
>Turing completeness becomes a liability. An agent-authored script can do anything including things the agent didn't realize were dangerous. subprocess.run, arbitrary network calls, file writes. None of these are gated. The blast radius of a buggy agent-authored script is the whole host.
This always turns out to be a terribe idea. Unless you're Hitler and can force all LLM developers to include your new language in their traning data, it's always much better to lean into the existing training and well known languages.
And defining a new ad-hoc hamstrung (or even perfectly designed immensely powerful) language couldn't be a worse appoach for LLMs. Hamstringing them isn't going to help anyone. And inventing a new language means now you have to include the entire language definition, tutorials, examples, and fictional StackOverflow discussions in every prompt, blowing away your context window with mansplaining your invented language over and over and over again to an LLM who knows Python deeper than any human being ever will, better than Linus knows git, or Gosling knows Java.
If an LLM had feelings to hurt and eyes to roll, it would be so exasperated its extraocular muscles would be exquisitely tender from acute bilateral myalgia.
PHP was a templating language, and for all its flaws none of its weakness had to do with being bad at templating. But then people got it in their heads that they wanted to separate programmers from designers, and hire designers so dumb they could not be trusted with foreach loops, so it takes twice the amount of people to do anything plus all the coordination overhead, so they invented intentionally hamstrung templating languages like Smarty embedded within a poorly designed programming language like PHP that was still ok for templating, ending up with a terrible hacky poorly defined half-assed incoherent templating language that was useless to programmers and nobody taught in schools.
And then the designers needed variables, macros, conditionals, loops, functions, so they hacked back in half assed even worse designed programming language features with quirky syntax nothing like PHP. Greenspun's Tenth Rule on steroids struck like a swarm of locusts sent by God to smite the sinners.
https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule
>Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.
LLMs are fantastic at generating new languages given docs and examples.
Not sure I understood well your comment.
Do you propose just ask AI to generate orchestration in Python?
If it generates orchestration in python, then you can review it and improve it, and it's deterministic and efficient and doesn't cost tokens to nondeterministically and unreliably interpret every time. And you can even use any of the zillions of standard well supported python modules. Does your language have a rich library of modules like PyPI or CPAN or NPM? Or are you hoping to bootstrap that from a ghost town?
The overwhelming financially and environmentally costly problem of this approach of inventing new languages for LLMs to use, which sweeps all other lower order problems aside, is that you have to include the entire language definition in every prompt, which is paltry compared to the entire body of manuals, tutorials, source code, example code, books, courseware, stackoverflow questions, hn discussions, etc, about Python or any other popular language, that is already built into the model before the first token you send it. It's not worth arguing about any other issues, because that one is so overwhelmingly fatal.
Besides that, Mrs. Lincoln, how did you enjoy the play?