lupodevelop

Author here. This started as a concept for user-written functions in Arke (https://github.com/arkemis/arke), an open-source backend-as-a-service written in Elixir. I'm not part of Arkemis, I just like contributing to their projects. It's a proof of concept and the code isn't published.

I'm posting it as a starting point for discussion. There are several ways to implement this and some look less viable than others, so I'd like to hear which ones you'd pick and where this one breaks.

The two parts I care about: a function starts with zero capabilities and only gets what's in the WIT world, and every function is a row, so on boot the node rebuilds routes, cron and triggers from the table.

I think the docs cover this. They assume on purpose that the program never touches a proxy, so the proof only holds if that's true. To me that's the more interesting thing to argue about, what the proof assumes, not whether the author knows TS is unsound.

Looking at the README, it seems to have one. With strict on and noUncheckedIndexedAccess off, tsc is fine with this:

  export function stale(xs: string[]): string {
    const n = xs.length;
    xs.pop();
    return xs[n - 1];
  }

You get undefined at runtime even though the signature says string. TScert won't take it unless you admit it in the return type, with string | undefined.

I had a huge stack of ancient mixed floppies!

I had done something “similar” with my virtualization system on macOS. You might find it interesting.

https://x.com/lupodevelop/status/2076334842061480369

It's intended for all developers in the BEAM ecosystem. Feedback would be great!

Graphics are fun and interesting. Nice Job.

I don't know. mixed feelings... but fine