I personally wish we could make a language LLMs would stay away from, rather than make it easier...
That’s easy – just use a language that is not popular enough to have a lot of training data.
Aperio Lang
11–19 of 19 posts
Re: Aperio Lang
#12This feels a lot like P / Pony / rospy. Not only that the "loci as hypergraph" framing also has a faint Milner's bigraphs feeling.
Re: Aperio Lang
#13> The structural correspondence is the point. > The choice of @form(vec) here is itself a real design decision, not an arbitrary one. > The point of the surface isn’t completeness — it’s that every distinct kind of structural commitment a unit can make has a syntactic home. ... Each commitment is declared, not inferred from code. > type is pure shape. A record. No lifecycle, no flow, no state machine, no bus particip…
Good catch! You want me to rewrite the paragraph to sound less like an LLM? (sigh)
Re: Aperio Lang
#14I feel dirty using emdash as the discriminator between human effort and non-effort. But it sure has quite a few.
I've been using the em-dash for years, having started doing so well before the dawn of LLMs -- needless to say the fact it is used as a telltale sign of LLM writing, doesn't gladden me one bit. Also because I value concise writing through picking correct grammatical elements -- like the em-dash.
Yep, me too. I’m annoyed that proper punctuation and even grammar have been co-opted by LLMs and now serve as a “tell.”
Re: Aperio Lang
#15Read through the intro and didn't understand a thing. Either I am dumb or this is dumb or both.
You’re not dumb.
Re: Aperio Lang
#16Re: Aperio Lang
#17Claude, make me a language that's optimized for the LLM era and matches both a human and Agent's mental model of the system the code is specifying. Like, it encodes systems with data that communicate with each other, no need to wire up implementation details like Rust's channels or specify wire formats and stuff. Give it a cool Latin name.
> The user wants me to re-invent Smalltalk—but with Latin names—for the "LLM era." Plan: I'll use the word "loci" in place of "actor" or "object" and call the language "Aperio" (Latin for "to explain something unknown," in this case referring to explaining Smalltalk and Actor systems to the user who has apparently never heard of them).
Re: Aperio Lang
#18The claim that existing languages add inefficiency for LLM's lacks supporting evidence. The complexity of software engineering, both for people and LLM's, comes from issues other than syntax.
Re: Aperio Lang
#19> The structural correspondence is the point. > The choice of @form(vec) here is itself a real design decision, not an arbitrary one. > The point of the surface isn’t completeness — it’s that every distinct kind of structural commitment a unit can make has a syntactic home. ... Each commitment is declared, not inferred from code. > type is pure shape. A record. No lifecycle, no flow, no state machine, no bus particip…
Just look at the PR it literally says claude wrote it
There recently was a change to VSCode where commits are being co-authored even if AI wasn't used. Not saying that AI wasn't used in this case, but it could be ambigious.
https://www.reddit.com/r/antiai/comments/1t1sj98/copilot_is_...