The benchmarks aren't great, they're super specific to sem's output: why would I ask Claude how many "entities" were modified by a commit and do I need a tool specifically for this request ? Note that an "entity" is a sem-specific concept...
> our implementation is it only prunes calls from > 3 user messages ago, if context is > 40K, and only if there's at least 20K tokens to be removed
Seems reasonable to me and explains why I can have long sessions (way longer than with zed agents) while still hitting cache. Opencode is just missing per-provider TTL.
Directly emitting metrics using OTLP instead of having the OTel receiver scrape the metrics endpoint is interesting.
I never made that move because the Prometheus metrics endpoint works and is so simple, and it's what most projects (eg kubernetes) use.
I was the sole DevOps at my company for a long time, the team is now bigger.
I used terraform for AWS and pulumi for K8S (terraform was too restrictive).
IMO pulumi is a huge gain of productivity when you know what you're doing.
Cons:
* It's plagued by bugs and the pulumi-kubernetes provider is not getting enough attention from the pulumi team (they're always working on compatibility with yet another language instead of focusing on one thing)
* You end up with your very specific/personal codebase instead of having a generic/standard thing
Still, no regrets, I saved so much time thanks to pulumi!
With a bigger team:
* Oboarding people takes more time
* You end up with code quality issues. Most "DevOps" people aren't devs, sadly.
How is garage for a simple local dev env ?
I recently used seaweedfs since they have a super simple minimal setup compared to garage which seemed to require a config file just to get started.
I ran into:
- too high memory usage
- no warning when a task doesn't yield
- monkey patching:
* general confusion like threading.local behaving differently
* pain to integrate sentry in gunicorn with gevent since you need to import sentry after monkey patching. The OTel libs work better but you need to be careful
* all compiled libs need to be replaced (eg psycogreen)
...
Building a framework on a non-async foundation (flask) in 2025 is bizarre.
The only way to scale a flask API is to use gevent, which is just problems waiting to happen. Asyncio is just better, safer and has been adopted by the industry.
This announcement contains so many fake marketing words I can't help but read it in DJT's voice...
Add Tim Apple's present and yeah, cool tech, not interested.
The main issue is podman support on Ubuntu.
Ubuntu ships outdated podman versions that don't work out of the box.
So I use podman v5, GitHub actions uses podman v3, and my coworkers on Ubuntu use docker.
So now my script must work with old podman, recent podman and docker
I'm in the position where I have to run a WAF to pass security certifications.
The only open source WAFs are modsecurity and it's beta successor, coraza.
These things are dumb, they just use OWASP's coreruleset which is a big pile of unreadable garbage.