News for hackers. Stuff that matters.

select1dev

Show HN: Zpup – Zdog style 3D scenes in JSON, SVG from any angle

https://github.com/rxolve/zpup

HI. I made small project called Zpup. It takes small 3D scene written in JSON and gives back a flat SVG from any angle. There is no JavaScript in the file, so it works in img-tag or README.I needed 3D for small project at my company, and Zdog make big impression on me. But Zdog has not been released for several years, so I wanted to make modern version.One thing works different. Zdog sorts each...

( Read More... | no comments | 2 points | on HN )
I run a daily job that clones and runs a freshly launched open-source project in a sandbox, so a few notes from the consumer side of this market.

Your point about bursty CPU matches what I see: install and build spike for 20–60 seconds, then the process mostly idles while the harness reads output. RAM only matters the day a project pulls in a headless browser.

The things that actually cost me time were not CPU or RAM, though. First, network policy. I run untrusted code with an egress allowlist, and most launched projects assume open internet, so the useful knob is per-sandbox allowlist editing with a proxy for package registries, not more memory. Second, environment hygiene. The sandbox needs a clean env with no inherited secrets, and a persistent sandbox that does not pick up changed env vars or allowlist entries without a restart bit me more than once. Third, a wall-clock timebox per run, because a stuck npm install behind a proxy fails silently rather than loudly.

Two questions: can a sandbox’s egress allowlist be changed while it is running, and when gVisor does not support a workload (you mention Docker-in-Docker), does the API fail fast or does the job just hang?