is where all the linux fortunes get injected with new electrons, new spins, new universe fairy dust to have a second eternal life?
Any conversation
Well I am starting a journey to learn LaTeX, took me time to get convinced on used it (I know) but let's see how it goes, again life showing me is never too late to learn something new
ะฆะฒะตัะพะบ ัะพะทั ะฝะต ะธะทะดะฐะตั ะณะพะปะพัะฐ, ะฐ ะฑะปะฐะณะพัั
ะฐะฝะธะต ะตะณะพ ะดะฐะปะตะบะพ ัะฐัั
ะพะดะธััั ะผะพะปัะฐ; ัะฐะบ ะฝะฐะดะพ ะถะธัั ะธ ะฒัะตะผ ั
ัะธััะธะฐะฝะฐะผ.
โะกะฒััะธัะตะปั ะคะตะพัะฐะฝ ะะฐัะฒะพัะฝะธะบ
The rose flower makes no sound, but its fragrance spreads far and wide in silence; so should all Christians live.
โSt. Theophan the Recluse
Vรฅr konges livsgjerning gรฅr mot slutten, landet samler seg for รฅ ta farvel med en konge som har vรฆrt samlende og god for landet. Mรฅ Gud velsigne hans minne og hans etterfรธlger.
Our king's life's work is coming to an end, the country comes together to say goodbye to a king who has been unifying and good for the country. May God bless his memory and his successor.
a constant, existential pull
so old I couldn't tell you the end
or draw its shape
between kind acceptance
and striving, struggling, writhing, climbing
learning, growing, discontent
"do you feel this way, too, at endless war with longing itself?"
but the birds and trees and ants and wind
in their own marvelous design
don't reply
Really glad to be using Haskell for work - especially in today's climate with agentic coding.
Our team uses containers to keep our development environment consistent across team members, though, and most agent sandbox approaches want to either offload your work fully to the cloud or they want to sandbox the agent harness process itself.
We're not ready for full cloud based development (yet?) and sandboxing just the agent doesn't work for us when the agent needs to run docker.
... because letting the agent run docker gives them a too-easy escape hatch from their sandbox.
So we're currently stuck with using VMs. This turns out to be tricky but seems do-able.
My current approach is to provision a VM image and use Incus for the execution. My main goal is to keep my current workflow of local/non-agent dev working seamlessly and share the source with the VM/agent.
This means sharing my working dirs with the agent VM but overlaying artifact dirs from VM-owned block devices so we don't take too big of an IO perf hit.
I also don't want the agent to be able to
git push so that means we need some quirky git config to rewrite origin paths and thread through some agent specific PATs ("thanks" GitHub) for read-only repo access. These ALSO need to be threaded through to the development containers - they need to clone private repos.... in the end, this seems to work but I haven't lived with it for long.
There are still some quality of life issues to work out, but I think it'll work out.
At this point, I've removed all coding agents from my host - and that's nice.
Curious, why does using Haskell make a difference here?
It's tangential to the sandboxing topic, really. I started the first post with a broader intent in mind and then elaborated on the sandboxing setup I'm working on.
For AI-assisted coding, though, it's nice because Haskell provides a lot of feedback earlier in the development process compared to lots of other languages. It tends to work once it compiles (obviously not all the time).