danappelxx

Wow, thanks for sharing, fun benchmark!

How does the agent auth with 1pw? How do you give it access to only the credentials it needs, with an approval flow and revocation? Who renews the token? You’ll likely end up reinventing something pretty close to what MCP is building towards.

Authn/authz is one of those things that can be really simple for pointed use cases but gets really complex when you need to support everything.

There is natural incentive for engineers working on a project to keep Claude skills up to date. I cannot say the same for general documentation.

GitHub API is actually quite tricky here because there is a different between “comment” and “review” and “review comment” (paraphrasing, I don’t remember the details). So it’s not as simple as one API call that grabs the markdown. Of course you can write a creative one-liner to extract what you need, though.

If the DNS resolution call blocks the thread, then you need N worker threads to perform N DNS calls. Threads aren’t free, so this is suboptimal. OTOH some thread pools e.g. libdispatch on Apple operating systems will spawn new threads on demand to prevent starvation, so this _can_ be viable. Though of course this can lead to thread explosion which may be even more problematic depending on the use case. In libcurl’s situation, spawning a million threads is probably even worse than a memory leak, which is worse than long timeouts.

In general, what you really want is for the API call to be nonblocking so you’re not forced to burn a thread.

Mirrors my experience. IPv6 issues are frustratingly hard to triage and reproduce, lots of “works on my machine” etc.

This is an interesting point. Hangs usually cost $ from user experience, with serverless they cost $ from compute. All the more reason to set strict deadlines on all API calls!

Took the same class at UCI (with Prof Anton Burtsev). Best class I ever took.

Yup, exactly. Phones change wifi networks, routers drop packets, load balancers get overloaded. Hard to fully eliminate tail latencies.

Unless your database is in the browser, you are always going to be at mercy of network latencies talking to the backend.

I think you always need loading states to account for slow network, or am I missing something?

“Cabin Noise during Acceleration with Ludicrous Enabled” was by far the most interesting

Generally stems from the philosophy that code is read more than written, and this helps readability.

What do you use instead?

Not that difficult, but it’s still a separate dependency (with python requirements). If the goal here is a Caddy competitor, then IMO it’s missing the mark in terms of “one stop shop”. What’s the killer feature?