I'm curious about the focus on the language design and features with regards to agent orchestration vs. being a general purpose/ML architecture oriented language. The headline examples go "Agent hook", "Async HTTP with retry", and then "FFT on tensors", and that last one seems different from the others. It's easy to imagine Mog being the backbone of agent coordination in a project using more standard languages, so I imagined that would be its role; but then I'd expect primitives/abstractions to be more geared towards this role specifically. For instance, a rich subprocess interface with special handling of stdin/stderr and maybe process interaction and lifecycle is something I'd expect to see before tensors and math-y stuff. Is the goal for Mog to ultimately be a general purpose language designed for LLMs to write, or one meant for agentic harnesses and orchestration/integration?
Show HN: The Mog Programming Language
81–90 of 91 posts
Re: Show HN: The Mog Programming Language
#82> If the host wants the Mog program to be able to do I/O, it has to supply the functions that the Mog program will call.
Have you considered implementing this in terms of algebraic effects? After all, controlling side effects is not only useful at the boundary between host and agent-generated code but also within any given code base to separate pure from non-pure code. I suspect that functional code will be much easier to understand for LLMs at scale because of state locality. (I actually suspect the same for humans but it's hard to obtain good data to answer this.)
Re: Show HN: The Mog Programming Language
#83Earlier quoted context omitted.
If you keep running these bots we will ban your main account as well. Please stop now. https://news.ycombinator.com/newsguidelines.html#generated
I'm asking this with probably half curiosity and half rhetorical intent but....why even give a warning?
If you stepped over a line you didn't know.. wouldn't you prefer a kind reminder rather than a sudden loss of access?
Re: Show HN: The Mog Programming Language
#84Earlier quoted context omitted.
It's a legitimate question to ask about any new language post AI - given there is no training dataset, any other language would work better with AI. The bigger problem is maintainability over the long term, Deno is built by Node.js creator and is maintained for half a decade now, that's hard to compete with. In a way it's much more about social trust rather than particular syntax.
Coding is a verifiable domain, so I think you actually have it backwards on that first point. We can now synthesize Stack Overflow sized datasets for an arbitrary new language, and use those to train LLMs to understand it. It's expensive of course, but if a new language is genuinely better for LLMs to write and understand, that would not be an issue.
Re: Show HN: The Mog Programming Language
#85Earlier quoted context omitted.
It's a legitimate question to ask about any new language post AI - given there is no training dataset, any other language would work better with AI. The bigger problem is maintainability over the long term, Deno is built by Node.js creator and is maintained for half a decade now, that's hard to compete with. In a way it's much more about social trust rather than particular syntax.
> given there is no training dataset, any other language would work better with AI. I guess it depends on what "would work better" really means, but I don't think it's always a given. I've made my own languages, there is no available training set on exactly those, but AI with a prompt can figure out how to effectively use them as much as any other language, it seems to me. I guess it helps that most languages are mor…
Re: Show HN: The Mog Programming Language
#86Earlier quoted context omitted.
Coding is a verifiable domain, so I think you actually have it backwards on that first point. We can now synthesize Stack Overflow sized datasets for an arbitrary new language, and use those to train LLMs to understand it. It's expensive of course, but if a new language is genuinely better for LLMs to write and understand, that would not be an issue.
Synthetic codebases are certainly an option, but if top models remain closed I don’t see them building datasets for every new language.
But compared to the immense amount of effort that goes into convincing a critical mass of humans to learn and write about your new language, and using _that_ material to train an LLM, I think it's fair to say things have gotten easier, not harder.
Re: Show HN: The Mog Programming Language
#87Re: Show HN: The Mog Programming Language
#88Re: Show HN: The Mog Programming Language
#89Now I wonder, shall we as humans still be able to read and review this code or is the sandbox + permission model as last line of defense sufficient?
The 3,200 token specification is not a formal one, I wonder whether having it formalized into a real grammar would help LLMs to generate code?
Re: Show HN: The Mog Programming Language
#90A complementary angle we've been exploring with LucidShark (lucidshark.com) is attacking the same problem from the workflow layer rather than the language layer: instead of constraining what the LLM can write, you run SAST, SCA, and linting automatically after every generation step, before anything touches CI or production.
The nice thing about that approach is it works with existing languages today — Python, TypeScript, Go, etc. and plugs directly into Claude Code or Cursor as a pre-commit gate. The downside is it's catching issues after generation vs. preventing them structurally like Mog aims to.
I suspect the long-term solution is both layers: safer languages for greenfield AI-native projects + robust static analysis for the 99% of existing codebases where you can't change the language.