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…
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…
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?
Ah, good to know!
It’s becoming standard as a security measure. See: Kata containers, Firecracker VM
I’ll assume the worst case: - lots of containers running on a single host - containers are each isolated in a VM (aka virtualized) - workloads are not homogenous and change often (your neighbor today may not be your…
IMO if you’re concerned about performance and yet are deploying databases this way — mmap should not even be on the radar.
Who is deploying databases in containers?
Agreed, but if you’re asking for a solution that will generate a spec from your code, the more proven path is to generate code from a spec. Gives you more and costs less. In my opinion the problem is that there’s some…
I suspect OpenAPI advocates would argue you should start with the spec and use it to generate both the client and server. This is already a common pattern in other RPC definition languages such as gRPC. You _could_…
does it add support for streams?
Right! Which is why we use (public) short-lived JWTs and (private) long-lived refresh tokens. What’s missing?
Interesting. You already don’t have to worry about revoking JWTs if they’re sufficiently short lived. This gives you the exact level of protection as a short-lived mTLS cert, because if that gets stolen the attacker can…
How does this approach practically differ from using short-lived JWTs+TLS?
This is incorrect, value types are not referenced counted in Swift. If a value type contains a reference type member (usually an anti pattern!), then that member’s reference count is indeed incremented when the value…
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…
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…
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?
Ah, good to know!
It’s becoming standard as a security measure. See: Kata containers, Firecracker VM
I’ll assume the worst case: - lots of containers running on a single host - containers are each isolated in a VM (aka virtualized) - workloads are not homogenous and change often (your neighbor today may not be your…
IMO if you’re concerned about performance and yet are deploying databases this way — mmap should not even be on the radar.
Who is deploying databases in containers?
Agreed, but if you’re asking for a solution that will generate a spec from your code, the more proven path is to generate code from a spec. Gives you more and costs less. In my opinion the problem is that there’s some…
I suspect OpenAPI advocates would argue you should start with the spec and use it to generate both the client and server. This is already a common pattern in other RPC definition languages such as gRPC. You _could_…
does it add support for streams?
Right! Which is why we use (public) short-lived JWTs and (private) long-lived refresh tokens. What’s missing?
Interesting. You already don’t have to worry about revoking JWTs if they’re sufficiently short lived. This gives you the exact level of protection as a short-lived mTLS cert, because if that gets stolen the attacker can…
How does this approach practically differ from using short-lived JWTs+TLS?
This is incorrect, value types are not referenced counted in Swift. If a value type contains a reference type member (usually an anti pattern!), then that member’s reference count is indeed incremented when the value…