conroy

https://gleam.run/ - Gleam is a friendly language for building type-safe systems that scale!

Maintainer of sqlc here. Thanks for the kind words! I'm considering switching to the sqlx model of talking to a running database simply because trying to re-implement PostgreSQL internals has been a huge challenge. It works for most queries, but for the long tail of features, it's a losing battle.

Can you tell me why it's a non-starter for you?

We're in us-west-1 and seeing issues across Cloud Run, Cloud SQL, Cloud Storage and Compute Engine.

you'd be surprised, but there's actually a bunch of problems you can solve with something like this, as long as you have a safe place to run the generated code

Riza | San Francisco | Full-Time | System, Backend, and Full-Stack Engineers | https://riza.io

We provide isolated runtimes for executing untrusted code, mostly generated by LLMs. Our sandboxing is powered by a combination of WebAssembly, V8, and microVMs. Our customers do things like extract data from log lines at run time by asking claude-3-7-sonnet to generate a parsing function on-the-fly and then sending it to us for execution.

Things we need help with:

- Our API (https://docs.riza.io/) (Postgres / Go)

- Our account dashboard (Postgres / Go / React / TypeScript)

- Our code execution engine (Go / Rust)

- New products including code generation workflows (Anthropic / OpenAI experience a plus)

We’ve raised seed money, but the whole company is currently just me, Andrew and David working out of a converted warehouse on Alabama St. We’re second-time founders, so we know the risk we’re asking you to take and we’re prepared to compensate accordingly.

See open roles and apply here: https://jobs.ashbyhq.com/riza

Remote MCP servers are still in a strange space. Anthropic updated the MCP spec about a month ago with a new Streamable HTTP transport, but it doesn't appear that Claude supports that transport yet.

When I hooked up our remote MCP server, Claude sends a GET request to the endpoint. According to the spec, clients that want to support both transports should first attempt to POST an InitializeRequest to the server URL. If that returns a 4xx, it should then assume the SSE integration.

Riza | San Francisco | Full-Time | System, Backend, and Full-Stack Engineers | https://riza.io

We provide isolated runtimes for executing untrusted code, mostly generated by LLMs. Our sandboxing is powered by a combination of WebAssembly, V8, and microVMs. Our customers do things like extract data from log lines at run time by asking claude-3-7-sonnet to generate a parsing function on-the-fly and then sending it to us for execution.

Things we need help with:

- Our API (https://docs.riza.io/) (Postgres / Go)

- Our account dashboard (Postgres / Go / React / TypeScript)

- Our code execution engine (Go / Rust)

- New products including code generation workflows (Anthropic / OpenAI experience a plus)

We’ve raised seed money, but the whole company is currently just me, Andrew and David working out of a converted warehouse on Alabama St. We’re second-time founders, so we know the risk we’re asking you to take and we’re prepared to compensate accordingly.

See open roles and apply here: https://jobs.ashbyhq.com/riza

Did a crazy thing and adopted Bazel for our two person company. Took a while to get everything working, but the average build takes about 30 seconds to run, across Go / Rust / TypeScript.

This is just a limitation of the wasmtime CLI. The full Rust API let's you mount filesystems as read-only. Not sure why it's not exposed as an argument.

wasmtime works as long as you make sure to include the lib directory

    % wasmtime run --dir .::/ python.wasm -c 'print("hello world")'
    hello world 

disclaimer: I run a code execution API service (https://riza.io/playground) that does this and more (HTTP, packages, etc.)

Make sure you're looking at the new schedules (https://www.caltrain.com/media/33909) which go into effect on September 21 of this year. The slowest trips between SF and Sunnyvale are ~65 minutes and the fastest is ~50 minutes.

I'm curious how this performs compared to River https://riverqueue.com/ https://news.ycombinator.com/item?id=38349716

You can see the latest stats here: https://bsky.jazco.dev/stats

Around 200,000 folks liked a post today.

> I would think a much less explodey way of shimming out untrusted code would be an in-memory filesystem so things blow up less

Filesystem access is the first item on our roadmap (https://docs.riza.io/reference/roadmap). If you want to see it in action, try opening /src/code.py. While adding an in-memory filesystem would be easy, we want to make it usable for reading and writing potentially large files.

> I guess put another way: who is the target audience for this?

Our customers are using our API to run LLM-generated code, build plugin systems, and power customer-defined data transformations.

In this case, a HTTP API is the abstraction. Integrating with ACH and other payment rails requires a lengthy integration process. Sometime you have to send binary files using FTP!