I do like Kagi but the Gemini deal was too good to pass up as it also gives my a code agent.
3,302 karma · joined May 3, 2014
I do like Kagi but the Gemini deal was too good to pass up as it also gives my a code agent.
I'm going to spend more time contributing without so much self-promotion.
Thanks for the feedback.
Idk, I already don’t bother with Opus and stick with sonnet med. I really care more about speed. I use qwen3.6 27b for personal projects and I think it works pretty great.
So like the article mentions, if scaling stalls and small models get better it’s not impossible to imagine a convergence and hardware costs drop.
Having said that, self hosting will be a niche thing like it is today for other services.
I just revamped the collaboration portion which is a patchbin service: https://pr.pico.sh
As part of that I work im also iterating on the ci/cd solution we are calling pici: https://ci.pico.sh
AMA
It's spawning PTYs but does it support SSH'ing into a remote session and running commands from a remote shell? That's something I built into zmx in order to scratch that "debugging in a remote VM" itch.
https://pico.sh/feeds is an ssh app that is an rss-to-email service.
Famous last words, but point is taken.
The non deterministic nature of an llm breaks the metaphor that they are like a compiler.
However, it’s not foreign to compilers to receive feedback from the running program (PGOs), so there are still parallels to the feedback we provide LLMs that guide their “optimization”.
I think even calling LLMs a non-deterministic compiler isn’t accurate either so ultimately I agree the metaphor doesn’t quite work.
I do think LLMs are like compilers in terms of how they changed how we build programs from a historical context. But that’s about it.
Sftp is still very useful even in 2026
That feels like a failure in the spec. Your example illustrates it: echo has unspecified behavior that literally prevents it from being portable.
Is it possible portability is just not a feature of posix?
This post was thought provoking, I wonder, is the hidden argument here that the posix spec for a shell is not well specified if there is so much variance between the implementations?
Or is the fundamental issue simply a matter of history? Both?
I don't understand how the coordinated process group works. Doesn't that mean in this multi-process mode it must be IPC? Maybe the claim "shared memory space" is more an architectural description than an OS-level claim?
Then I just update when I need to update