It had the usual functions and i/o library stuff. In fact I wrote a tool to absorb other library headers e.g. C or C++ and product blocks that my compiler could link with, and voila your program could call those external libraries.

We used it for a couple of contracts. Some of the control engineers were enthusiastic; some not so much. One more thing to learn.

I'd strongly recommend going over the README by hand. What you currently have is redundant and disorganized, and header sizes/depths don't make a lot of sense. The "manual build" instructions should also describe the dependencies that the install script is setting up.

You could take it a step further and have a deterministic agent inside a deterministic VM, and you can share a whole project as {model hash, vm image hash, prompt, source tree hash} and have someone else deterministically reproduce it.

Is this useful? Not sure. One use case I had in mind as a mechanism for distributing "forbidden software". You can't distribute software that violates DMCA, for example, but can you distribute a prompt?

If I have 10 bugs in production I can just regenerate my app and now I’ll have 10 completely different new bugs. New bugs on everyone’s machine! Fun for the whole family.

How does this handle multiple different “blocks” that need proper interfaces to communicate with each other.

I can only imagine the safety nightmares that would be generated in C++ this way.

Seriously…what is this for?

This seems to scratch that itch. The non determinism makes it probably not suitable for most uses, though.

I understand why that's the case, and I believe this is the main hurdle for adoption of a tool like this.

One example:

    Best of all, they work together. You can store your .glp blueprints in a Docker container—creating software that is immortal in both environment and logic.

What other language-agnostic methods of describing complex systems is your project inspired by? In competition with?

---

By using this tool, a programmer or team is sending the message that:

"We expect LLM generated code to remain a deeply coupled part of our delivery process, indefinitely"

But we didn't know about LLMs 5 years ago. What is the argument for defining your software in a way that depends on such a young technology? Most of the "safety" features here are related to how unsafe the tech itself still is.

"Nontrivial LLM driven rewrites of the code are expected, even encouraged"

Why is the speedy rewriting of a system in a new language such a popular flex these days? Is it because it looks impressive, and LLMs make it easy? It's so silly.

And if the language allows for limiting the code the LLM is allowed to modify, how is it going to help us keep our overall project language-agnostic?

> 1- installing with irm https://raw.githubusercontent.com/alonsovm44/glupe/master/in... | iex

That is high risk, don't ask people to do that, especially when it's completely unnecessary for what the language is, and the language isn't providing value, it's just esoterical.

>2. "Glupe isolates AI logic into semantic containers, so your manual code stays safe."

Watchout for light-AI psychosis. This existed before AI to be fair, but using words in a way that doesn't convey meaning. Maybe what's going on is that you use them with ChatGPT and it either understands or doesn't but follow along. So make sure to prioritize language that you develop with humans, not AI. And try to simplify your language and the message you were trying to convey, because you missed bigtime with that sentence.

>3. The language itself misses the mark. It looks like it's C++ with some modifications?

4- it's also not a language but a terminal? Try to get the trust of your users by doing one thing well before promising to do it all. A bit of humility pays off, you can't do everything anyways.