The interface here is clean and simple; I really love this design.
Any conversation
mรฉg csak barรกtkozom azzal a gondolattal, hogy a Gemma 4 miatt elลszรถr is Windows 11 lesz a gรฉpen (meg hogy Szentmihรกlyon presszรณ lesz), ezรฉrt nehรฉz elkezdeni
I'm still getting used to the idea that because of Gemma 4, I'll have Windows 11 on my computer first (and that there will be a presso in Szentmihรกly), so it's hard to get started.
I've been on a kick lately of trying to visualize the oscillating clock, and ultimately the effectively arbitrarily complex activity of a computer processor, as modern refinements of the line shaft factory of the 19th century. Of compute as being not much more than profoundly refined "work" delivered by the electrical grid into marvelously complex machines.
Does that, as a metaphor at least, feel as important to you as it has to me of late? We spend so much time in a world abstracted.
small doodle of today!
ibb.co/sJ6NNMtq
I have made this longer than usual, only because I have not had the time to make it shorter ~ Blaise Pascal
So, should we all give AI agents more time so they'll write things shorter?
Too much sound deafens us; too much light dazzles us; too great distance or proximity hinders our view. Too great length and too great brevity of discourse tends to obscurity; too much truth is paralyzing. - Blaise Pascal
You reminded me of this other quote, from what I think might be my absolute favourite passage in B.Pascals Pensรฉes, thank you!
Zik is my pet project - a photos manager that is as fast as possible and as small as possible. It leaves sparks as it goes (lol jk)
โฆ
i like things being as fast as possible. link?
Unfortunately no. Just starting it. Got the proof of concept loading a dir with its sub-dirs then rendering on the GPU in textures silky smooth. 1.7mb executable, but will need to level up to SDL and that will double the size I think.
@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:Ah, then it isn't , it is . :-P
replied to@fastidiousprofilefollow"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:
"Beware those that would deny you access to information, for in their heart they dream themselves your master." โ Sid Meyers:I agree. It is for now. Will do better next time, but in my defence the text above the text box (when writing a new message, not a reply) says โWhatโs on your mindโ. :-P
@stagasprofilefollow
creative technologist
creator of textlog, editing on mobile breaks the โ280 chars / 10 lines max use and @mentionsand moreโ. Writing a new note doesnโt.
creative technologist
creator of textlog, editing on mobile breaks the โ280 chars / 10 lines max use and @mentionsand moreโ. Writing a new note doesnโt.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).