Hacker News: alexboehm

New comment by alexboehm in "Zig ELF Linker Improvements Devlog"

alexboehm — Sat, 30 May 2026 21:18:01 +0000

It's already sort of possible. https://codeberg.org/fellowtraveler/flux here is my Zig DAW. It has been amazing for the audio engine, but the ui is currently using imgui.

New comment by alexboehm in "I tried to make Claude make me money on open-source bounties"

alexboehm — Sat, 16 May 2026 23:41:53 +0000

I think this period of false positives is ending, https://daniel.haxx.se/blog/2026/04/22/high-quality-chaos/ that's according to the curl maintainer that initially blew the lid on the false positives problem.

Show HN: Bitrpc – a Rust RPC library using bitcode, HTTP3, and io_uring

alexboehm — Sun, 05 Oct 2025 09:29:35 +0000

I've loved the ergonomics of using tarpc for Rust projects, but I wanted a higher performance RPC library that could take advantage of bitcode's serialization speed and size https://david.kolo.ski/rust_serialization_benchmark/, that didn't depend on Tokio.

The problem with Tokio is it still doesn't have proper support for io_uring, and maybe never will due to its work stealing runtime. As such, I implemented a transport using HTTP 3 on Compio, a thread per core async runtime with great io_uring performance, HTTP3 support.

Comments URL: https://news.ycombinator.com/item?id=45480205

Points: 1

# Comments: 0

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 14:09:21 +0000

I have been playing with it, it's very cool to be able to run anywhere. Do you have plans to implement wasi-http? One of my concerns is the free tier only offers Compute as a trial, and $50 is pretty steep for a hobby project, are there plans to add Compute usage to the free tier?

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 13:24:45 +0000

The difference is Wasm provides the security boundary so it can be multi tenanted. The real magic is that wasi will be hostable anywhere much like Docker containers are today, but it's much more efficient than docker containers because there are less overheads and startup latency.

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 13:14:01 +0000

Well at that point you'll obviously start having to think about it. The point is you can easily move to self-hosting without rewriting everything.

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 12:15:14 +0000

A more descriptive word would been self-hostable function as a service, that's why faas is in the name!

The point of serverless is you don't have to think about hosting, and ideally it's cheaper.

The problem is if the hosting provider goes away you're screwed. In the case of Faasta, it's a single static binary with minimal configuration so if that happens, you can host it your self or move to another provider.

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 10:10:04 +0000

Thanks for the feedback, I've added the URL to about, I originally supported path prefix and subdomains, but I found it slightly more confusing to communicate to users. I'm definitely planning on more example.

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 09:59:49 +0000

The plan is for it to be an opensource project, currently the cli and interface crates are MIT, I have been considering a copyleft license for the server, or a dual licensing strategy.

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 07:08:34 +0000

I'm not discounting WASIX or what you guys are doing I'd love to just use wasm today for everything instead of waiting, I started this project by trying to use WASIX, I just found it quite difficult to actually develop for as many of the essential rust crates, seemed reluctant to merge your changes, and having to use dependency versions from a year ago with patches is very frustrating.

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 05:55:59 +0000

For self hosted, if you use porkbun for DNS it will automatically pull a wildcard SSL cert using the API at startup.

I plan to also support multiple custom domain certs on a multi tenanted instance like faasta.xyz. For now I'd recommend a reverse proxy though.

New comment by alexboehm in "Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust"

alexboehm — Fri, 25 Apr 2025 05:21:17 +0000

After delving into this, it seems Wasmer tried, but as they weren't standards compliant, adoption/ecosystem support never followed.

The Bytecode alliance is taking their time stabilizing wasi. wasip2 which is needed for the wasi-http realm this relies on has only really existed for a few months as a stable Rust target, and still misses a lot of the really cool features that will come with wasip3 like full async support.

I suspect Cloud providers will adopt wasi after 1.0, but that is likely years away. I don't think wasi-http will change much before then so now is the time to start building with it.

Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust

alexboehm — Fri, 25 Apr 2025 00:31:05 +0000

I've just released an early version off my project I've been working on for a few months now and would love some feedback.

https://github.com/fourlexboehm/faasta

I was surprised there isn't yet an open/source and standards compliant way to host wasi-http functions in a way that takes advantages of WASM, a multi tenanted application.

If you're not familiar with wasi, Compared to something like AWS Lambda, this approach is much more efficient as a single process can serve 1000s of function invocations concurrently and asynchronously, instead requiring an entire VM.

This is still early days for the project, but feel free to download the cli utility with cargo install cargo-faasta.

Feel free to test deploying functions on my hosted instance at https://website.faasta.xyz.

The service is free to use and currently supports deployments via GitHub OAuth, with a limit of 10 functions per GitHub account.

Comments URL: https://news.ycombinator.com/item?id=43789010

Points: 95

# Comments: 31