The sandbox function should be similiar to Lua, right?
Show HN: The Mog Programming Language
71–80 of 91 posts
Re: Show HN: The Mog Programming Language
#72For me this is Gleam. Fairly small lang, type safe, compiled, NO NULLS (very important IMO), good FFI, code is readable, and... you get the BEAM! Agents can pretty much iterate on their own. The most important thing for me, at least for now (and IMO the foreseeable future) is being able to review and read the output code clearly. I am the bottleneck in the agent -> human loop, so optimizing for that by producing clea…
no nulls is truly not a problem. Of all the problems I have seen, I have never seen Claude mess up with nulls in Elixir.
Re: Show HN: The Mog Programming Language
#73Very cool!
The permission model is almost identical to Roc's - https://www.roc-lang.org/platforms - although Roc isn't designed for "Syntax only an AI could love" (among many other differences between the two languages - but still, there are very few languages taking this approach to permissions).
If you're curious, I've talked about details of how Roc's permission model works in other places, most recently in this interview: https://youtu.be/gs7OLhdZJvk?si=wTFI7Ja85qdXJWiW
Re: Show HN: The Mog Programming Language
#74I swear, if I see another Claude-generated "programming language", I'm going to barf.
Re: Show HN: The Mog Programming Language
#75This language could mog the ASU frat leader into a career ending cortisol spike. Clav finally has some clapback after getting trolled by an foids all day.
I pay my internet bills for this
Re: Show HN: The Mog Programming Language
#76[flagged]
Re: Show HN: The Mog Programming Language
#77The capability-based permission propagation is the part I'd want to stress-test first, in practice we found that the interesting failure mode isn't the agent escaping its sandbox, it's the agent calling back into the host in ways that are technically permitted but semantically wrong
Re: Show HN: The Mog Programming Language
#78Earlier quoted context omitted.
How's Gleam's IO story today? Still need to go via OTP?
Under the hood you're still calling into BEAM/OTP but most operations are covered in gleam, at least I've very rarely needed to FFI into Erlang (couple times to extend what a library provides with a custom edge case). gleam/io, mist, gleam/otp, sqlight, gleam_pgo, etc.
gleam/io doesn't actually support file IO, though, does it? Only printing to stdout.
So you'd need to use FFI just to write to disk, right?
Re: Show HN: The Mog Programming Language
#79Earlier quoted context omitted.
Under the hood you're still calling into BEAM/OTP but most operations are covered in gleam, at least I've very rarely needed to FFI into Erlang (couple times to extend what a library provides with a custom edge case). gleam/io, mist, gleam/otp, sqlight, gleam_pgo, etc.
gleam/io doesn't actually support file IO, though, does it? Only printing to stdout. So you'd need to use FFI just to write to disk, right?
There’s simplifile