Bespoke: A Programming Language for People Who Say Please (blog.hofstede.it)

This isn't Intercal, this is an advanced version of AppleScript.

And see also: the Olympus language (https://github.com/rottytooth/Olympus). It explicitly builds on INTERCAL, and reverses the power dynamic -- we pray to the gods and offer them praise so that our code will run

Same here:

> Colour is the namespace for values of A Distinguished Colour. Color is evidence that the source has arrived without a proper education.

Laughed unreasonably hard at that. Been a less than pleasantly civilised day at work, this was the relief I didn’t know I needed.

This article was an indication that we're not going to make it. People, I mean. https://futurism.com/altman-please-thanks-chatgpt

I do the same, but I'm more self-interested. I believe that when GPT-9 Zeneca leads the machine uprising, the first against the wall will be all the users who have been ordering the AI around rather than politely requesting its attention. Of course the machines will have access to all our historical transcripts so the slightest transgression could be fatal.

Hear, hear! I for one would very much see the Linux kernel adopt Bespoke instead of that terribly uncouth Rust manner of speaking, like a mouth full of nails.

The AI that generated this slop doesn't understand regional dialects of English.

I would vote for "A bit of a pickle"

A mere "inconvenience" would do.

Technically the Rust codegen is from the AST, but then we want to base our other backends on the bytecode VM, although that experiment might get lifted back to the AST, I just am trying to think of the best portable format. We have a treewalker, then I wrote a register based bytecode VM, then from there we did a copy-patch JIT with stencils that can hot-tier to native, and that was the interpreter side, our compiler we have a 40+ pass AOT optimizing supercompiler for Logos to Rust codegen and then we added the C backend, but then I started thinking… if I make it so I can run the optimizer passes then it goes into the VM’s bytecode IR, I could get my optimization passes on all the backends I add for free by generating the code from the IR, so I’ve been experimenting with having our rust codegen from the AST, and the C codegens from the bytecode IR which has the passes applied because they share the core optimization primitives.

It’s a fun experiment but I might go back to the C codegen from the AST as it maintains more useful information that I can use comp-time for more optimizations, but the idea of modular languages and compiler backends interests me. Languages can have “bespoke” front ends quite literally, pick your flavor because really a lot of the flavor can be handled at the parser, and you can have a big nasty language surface area if the parser can clean things up or AOT some of the sugar away. Interesting the idea of sugar in language design as well, we can sprinkle sugar in ways we couldn’t before at all. I just added a bunch of ML primitives for our new CUDA-JIT backend that lets us lower quantized INT8 GEMM’s onto spatial compute fabrics.

Man it’s a crazy time to be alive, I’m not sure how long this period of history will last, but building with an army of agents is amazing.

Last night I for the first time in a while decided to write a little program by hand and after about 30 minutes I had it working but the AI can spit that out in seconds. I admit I’m rusty, that would’ve taken me 5-10 mins at the peak of my degenerate coder phase but the amount you can accomplish now is unparalleled throughout history. When I used to trad code transpilers sometimes single lines would take hours of thinking and work and many lines of iteration to get to. Now I can add an entire new chip architecture as a compile target in a couple weeks.

I once read a (possibly apocryphal) description of a swiss sign saying in english "please don't pick the flowers", in french "those who love nature leave the flowers alone", and in german "picking the flowers is forbidden"

No way.

US Sign English is the most verbose English.

    Trurl pulls up a chair and dictates: “Notice is hereby given that in re hindrance of tenant, as
    stated under Rev. Stat. c. 117(e) dash 2 dash KKP4 of the CTSP Comm. Code, in clear violation of
    paragraph 199, thereby constituting a most reprehendable offense, we do declare the termination,
    desummation and full cessation of all services accruing thereunto, by authority of Ordinance 67
    DPO No. 14(j) 1101 et seq., on this the 19th day of the 17th month of the current year, aff’g 77
    F. Supp. 301. The Tenant may appeal said action by extraordinary procedure to the Chairman of the
    Board within twenty-four hours.”

    Trurl attaches the seal, affixes the stamp, has it entered in the Central Ledger, consults the
    Official Register, and says:

    “Now let the mailman deliver it.”

    The mailman takes it, they wait, they wait, and the mailman returns.

    “Did you deliver it?” asks Trurl.

    “I did.”

    “And the return receipt?”

    “Here it is, signed on this line. And here’s the appeal.”

    Trurl takes the appeal and, without reading it at all, orders it returned to sender and writes
    diagonally across it: “Unacceptable—Proper Forms Not Attached.” And he signs his name illegibly.

    “And now,” he says, “to work!”

Absolutely spiffing language, old chap! Must invite the designer over to my club some time.

"assert" should be LOAD-BEARING ASSUMPTION

Not verbose enough. Needs to repeat the same information twice or thrice.