Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
benswerd
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
91.
▲
by
benswerd
6mo ago
I disagree (as a sandboxing company). With respect to the market, every single sandbox sucks. I'm not gonna shit talk competitors but there is not a good sandboxing platform out there yet — including me — compared to where we'll b
92.
▲
by
benswerd
6mo ago
We're not going after hobbyists. We're building the platform for companies like exe.dev to build on. Thats why its all usage based. That said, our $50 a month plan can be used as an individual for your coding agents, but I wouldn&
93.
▲
by
benswerd
6mo ago
So this is an ongoing optimization point, no perfect solution exists. Freestyle VMs work with a network namespace and virtual ethernet cable going into them, so they all think they are the same IP. This means that while complex protocol con
94.
▲
by
benswerd
6mo ago
Self hosting can be doable for constant small/medium size workloads You can handroll a lot with: https://github.com/nestybox/sysbox?tab=readme-ov-file https://gvisor.dev https://github.com&#
95.
▲
by
benswerd
6mo ago
Fly.io sprites is the most similar to us of the bunch. They do hardware virtualization as well, have comparable start times and are full Linux. What we call snapshots they call checkpoints. The big pros of Sprites over us is their advanced
96.
▲
by
benswerd
6mo ago
Reviewing this now. our public pricing at www.freestyle.sh/pricing seems to be working, can you point me in a more specific direction?
97.
▲
by
benswerd
6mo ago
I'm working on an article deep diving into the differences between all of us. I think the goal of Freestyle is to be the most powerful and most EC2 like of the bunch. Daytona runs on Sysbox ( https://github.com/nestybox&
98.
▲
by
benswerd
6mo ago
We're using copy on write with the memory itself. Fork time is completely decoupled from the size of the machine. Creating snapshots takes a 2-4 second interruption in the VM due to sheer IO that we didn't want here. Whats especia
99.
▲
Launch HN: Freestyle – Sandboxes for Coding Agents
(freestyle.sh)
322 points
by
benswerd
6mo ago
|
158 comments
100.
▲
by
benswerd
7mo ago
Made it with Vite+. Highly recommend trying it, rolldown HMR and build times are freakishly fast.
101.
▲
by
benswerd
7mo ago
I disagree with this. My team will send me random snippets from OSS libraries and we all go WTF what is that, and my team will also send really clever lines and we'll go wow. "Good code" is subjective, but good engineers have
102.
▲
by
benswerd
7mo ago
This is correct. Comments serve a purpose too, but they should only be used when code fails to self document which should be the exception.
103.
▲
by
benswerd
7mo ago
I write systems rust on the cutting edge all day. My work is building instant MicroVM sandboxes. I was shocked recently when it helped me diagnose a musl compile issue, fork a sys package, and rebuild large parts of it in 2 hours. Would
104.
▲
by
benswerd
7mo ago
I think this style of work will go away. I was skeptical but I now write the majority of my code through agents.
105.
▲
by
benswerd
7mo ago
Wrestled with this a bit. The struggle with this one in particular is its as much for people to read as it is for agents, and the agents are secondary in its case. I generally agree on this as best practice today, though I think it will bec
106.
▲
by
benswerd
7mo ago
I don't think testing the product alone is good enough, because when you give it tests it has to pass it prioritizes passing them at the expense of everything else — including code quality. I've seen it pull in random variables, b
107.
▲
by
benswerd
7mo ago
LOL fr. I've been talking with some friends about RL on chaos monkeying the codebase to benchmark on feature isolation for measuring good code.
108.
▲
Be intentional about how AI changes your codebase
(aicode.swerdlow.dev)
170 points
by
benswerd
7mo ago
|
102 comments
109.
▲
by
benswerd
7mo ago
I've seen a lot of people talking about how AI is making codebases worse. I reject that, people are making codebases worse by not being intentional about how their AI writes code. This is my take on how to not write slop.
110.
▲
RPyC – Transparent, symmetric distributed computing
(rpyc.readthedocs.io)
2 points
by
benswerd
8mo ago
|
0 comments
111.
▲
by
benswerd
8mo ago
I didn't get it until you said this
112.
▲
by
benswerd
8mo ago
The last year vs this year is crazy
113.
▲
by
benswerd
9mo ago
This is super basic, no caching or persistence at all, straight polling the streams and forwarding to the client. Would love to chat, my contact is public on my profile, send a msg.
114.
▲
by
benswerd
9mo ago
TBH not clear because I'm not clear on it. I believe the naming scheme is nonstandard across providers and not a requirement as part of the standards.
115.
▲
by
benswerd
9mo ago
I've been thinking a lot today about how these bots change with just a little bit more intelligence. Kinda terrifying.
116.
▲
Certificate Transparency Log Explorer
(certs.swerdlow.dev)
33 points
by
benswerd
9mo ago
|
10 comments
117.
▲
Favorite Rust Crates of 2025
(docs.freestyle.sh)
4 points
by
benswerd
9mo ago
|
0 comments
118.
▲
by
benswerd
9mo ago
I'm https://swerdlow.dev — love this
119.
▲
by
benswerd
10mo ago
It does not work on iOS Safari at all, it should show a warning at the top saying so
120.
▲
by
benswerd
10mo ago
MacOS Linux Windows or other?
More ›