Live data from Hacker News

Bespoke: A programming language for people who say please

blog.hofstede.it

21–30 of 47 posts

Re: Bespoke: A programming language for people who say please

#21

I might be a potential user. I find myself being polite in AI prompts sometimes. I guess it can’t hurt, just more practice at polite interactions. ( The prompt phrasing, not the language. )

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

Re: Bespoke: A programming language for people who say please

#22
Love this!! :) I thought about being that verbose in Logos lang, but I think language design changes a lot in the modern era.

I suspect we end up with modular compilers, v0.11.0 of logos lang coming soon with some big updates! We have one frontend which is our Logos language, then the intermediate representation a register VM Bytecode IR, then from that we generate Rust, C, and we have a JIT that will just in time directly to RISC-V, Tenstorrent, we’ve been messing with plasticine, and hoping to get our hands on some sambanova RDU’s. We’re burning our language to a chip.

For fun maybe I’ll add a bespoke dialect :p

https://logicaffeine.com/guide

Re: Bespoke: A programming language for people who say please

#23

Love this!! :) I thought about being that verbose in Logos lang, but I think language design changes a lot in the modern era. I suspect we end up with modular compilers, v0.11.0 of logos lang coming soon with some big updates! We have one frontend which is our Logos language, then the intermediate representation a register VM Bytecode IR, then from that we generate Rust, C, and we have a JIT that will just in time di…

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.

Re: Bespoke: A programming language for people who say please

#27

Idea first developed by intercal, which there are no reference to : https://en.wikipedia.org/wiki/INTERCAL

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

Re: Bespoke: A programming language for people who say please

#29

Love it. Compared to regular programming languages it reminds me of the difference between lawn signs in the US vs the UK: US: Keep Off Grass! UK: Please remain on the footpath for the sake of our lawn

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"

Re: Bespoke: A programming language for people who say please

#30

I might be a potential user. I find myself being polite in AI prompts sometimes. I guess it can’t hurt, just more practice at polite interactions. ( The prompt phrasing, not the language. )

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.
Post reply on HN