alexboehm

4 ms·

1.
by alexboehm 14d ago
Just try opencode, it comes with 1.3 contributor free.
2.
by alexboehm 29d ago
Fair point, but name one thing you can't do with bash.
3.
by alexboehm 29d ago
I too was frustrated with needing npm and slow startups or huge rust compile times for agents. I tried getting agents to write a tool like this with proper raw mode content pasting/ interruptions, but they just kept screwing it up with
4.
by alexboehm 2mo ago
Interesting, I've been building the inverse of this project, to enable running Linux binaries on macOS, as that's not something I've seen in an active project. It works an a very similar way but it's in Zig. I'll po
5.
by alexboehm 4mo ago
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.
6.
by alexboehm 4mo ago
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 pos
7.
Show HN: Bitrpc – a Rust RPC library using bitcode, HTTP3, and io_uring(github.com)
1 points by alexboehm 1y ago|0 comments
8.
by alexboehm 1y ago
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 ther
9.
by alexboehm 1y ago
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
10.
by alexboehm 1y ago
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.
11.
by alexboehm 1y ago
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
12.
by alexboehm 1y ago
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.
13.
by alexboehm 1y ago
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.
14.
by alexboehm 1y ago
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
15.
by alexboehm 1y ago
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 recommen
16.
by alexboehm 1y ago
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-h
17.
Show HN: Faasta – A self-hosted Serverless platform for WASM-wasi-HTTP in Rust(github.com)
95 points by alexboehm 1y ago|31 comments