Viewing profile — Horos

what about mcp cdp ? my claude drive his own brave autonomously, even for ui ?

right — no variance, question was off target. worth noting though: the sema-bounded WriteAt goroutines are structurally a fan-out over homogeneous units, even if the pipeline feels…

dead link ?

this makes sense for your workload, but may the right primitive be a function of your payload profile and business constraints ? in my case the problem doesn't arise because contro…

had a look ?

fair point on blocking sends — but that's an implementation detail, not a structural one. From my pov, the worker pool's job isn't to absorb saturation. it's to make capacity expli…

Isn't a dedicated worker pool with priority queues enough to get predictable P99 without leaving Go? If you fix N workers and control dispatch order yourself, the scheduler barely …

Thanks for sharing — always a pleasure to discover what others are building. A few thoughts after your answers: The E2E file sync part has existing solutions, and your access right…

even thoses replies create common value. Tomorow datasets. Keep publishing !

ACID & Idempotent. dataplane / controlplane. dryruns et runbook automations. llm does not act on production. he build scripts, and you take the greatest care of theses scripts. Clo…

who believe here that saying no is possible ?

The "job as library" pattern is simple: instead of wiring jobs into main or a framework, you split into 3 things. Your queue is a struct with New(db) — it knows submit, poll, compl…

And to put it plainly: we won't be able to manage LLM-generated contributions without LLMs. It's physically impossible at this scale. Which means the immune system has to be built …

Something worth sitting with, rather than a conclusion: As PR velocity reaches this scale — 100 per hour, hundreds of thousands of lines a day — I find myself wondering about the c…

I've set a fully async patern. blobs chunked into sqlite shards. It's a blind fire n forget go worker danse. wich can be hold as monitoreed or scale as multiple instances if needed…

Three real risks in your current approach before anything else. Shared references mutate silently — in JS, objects passed between your "tables" are aliases, not copies, so a mutati…

Quick question before going further: is this an exercise in language internals, or do you have a concrete use case in mind? Asking because the answer changes the architecture signi…

Nice try — the local-first distributed pattern worth building on. Three questions: Why blockchain for access rights? A signed Merkle structure or a Certificate Transparency-style l…