Good morning, techno.
Konstantin Scharf - Still Moving
Any conversation
My friend won 2nd place in the pc demo competition at Evoke in Kรถln this weekend, with his ascii-inspired demo Glyphnosis. Really happy for him! ๐ฅ
Added
#meta tag โ use it whenever you want to talk about the site itself, and these posts will not show up in all, any or the postโs page. Only those that follow the tag or the person will see these posts in my feed or in post pages. This is to keep the site clear of meta discussions which dominated a lot at this early stage and I think were annoying to many people. So this is the last meta without the #meta tag youโll see unless u follow. Iโll try to tag every post I find.de a tapasztalatok szerint a kezelลfelรผlet elfรกradรกsa elลbb-utรณbb magรกval hozza magรกnak a rendszernek az elfรกradรกsรกt, majd lassulรกsรกt, szerintem 1-2 รฉv mรบlva (amikor mรกr senki sem emlรฉkszik majd rรก), forradalmi รบjรญtรกskรฉnt visszahozzรกk a Windows 10 kezelลfelรผletรฉt Windows 12 nรฉven
but according to experience, the fatigue of the user interface will sooner or later lead to the fatigue and then the slowdown of the system itself. I think in 1-2 years (when no one will remember it anymore), they will bring back the Windows 10 user interface as a revolutionary innovation under the name Windows 12.
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).
The government welds your door shut and then outlaws starting a business and living in McMansions, cars, skyscrapers, and tiny homes.
The governments bans body odor and then closes stores and bans delivery services.
The state closes bathrooms and then outlaws public urination.
The government closes the border and then arrests tourists for overstaying their visas.
@fastidiousprofilefollow
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyersreplied to:ๅฝ็ถ๏ผใใใฆๆฅๆฌ่ชใงใ๏ผ
Of course! And in Japanese too!