!
Any conversation
I've been building a Markdown variant called Zd that's focused on extensibility and simplicity. I'm curious what you would change about Markdown if you were designing it from scratch, what challenges you face as a user, or what you wish were easier to do when incorporating Markdown into your own projects.
Definitely tables are cumbersome.
Yeah, 100%. That is completely something I am punting on currently. It would be easy to just copy over the solution from (extensions to) Markdown, but it's hard to entirely narrow in on both what tables ought to do and how to make them do it.
If you had a magic wand, what would you have them be more like?
everytime i see projects like this, i think that a rss implementation it wolud be so cool. Although iknow that there is not that much rss lover out there haha
ๆฅๆฌ่ช่ฉฑ่
ใฏใฉใใใใใใใใ ใใใใใใงๆฅๆฌ่ชใงๆธใ่พผใฟ็ถใใใฎใฏใฉใใชใใ ใใ
I wonder how many Japanese speakers there are. Is it okay to keep posting in Japanese here?
ใใใซใกใฏไธ็
Hello World
ใใใงๆฅๆฌ่ชใงๆธใ่พผใฟ็ถใใใฎใฏใฉใใชใใ ใใ
ใตใคใไฝๆ่
ใฏใใพใใพใฎ่จ่ชใฎ่ฉฑ่
ใไธ็ทใซ่ฉฑใใๅ ด้ขใซใใใๆฐใใใ
I wonder if it's okay to keep posting in Japanese here.
I get the feeling the site creator wants this to be a place where speakers of various languages can talk together.
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).
@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:Many pass by me. All combined arenโt worth $0.02. ๐