jaytaylor

I'm testing a theory that large-scale (LoC) generated projects in Rust tend to have fewer functional bugs compared to e.g. Go or Java because Rust as a language is a little stricter.

I've not yet formed a full opinion or conclusion, but in general I'm starting to prefer Rust.

Re: generalizing mocks, it sounds interesting but after getting full-fidelity clones of so many multi-billion dollar SaaS offerings, I really like it and am hooked. It pays nice dividends for developing using agentic coders at high scale. In a few more model releases having your own exhaustive DTU could become trivial.

The Go to Rust rewrite is interesting - was that driven by performance or more about the ecosystem/tooling for this kind of work?

I'm testing a theory that large-scale (LoC) generated projects in Rust tend to have fewer functional bugs compared to e.g. Go or Java because Rust as a language is a little stricter.

I've not yet formed a full opinion or conclusion, but in general I'm starting to prefer Rust.

Re: generalizing mocks, it sounds interesting but after getting full-fidelity clones of so many multi-billion dollar SaaS offerings, I really like it and am hooked. It pays nice dividends for developing using agentic coders at high scale. In a few more model releases having your own exhaustive DTU could become trivial.

(DTU creator here)

I did have an initial key insight which led to a repeatable strategy to ensure a high level of fidelity between DTU vs. the official canonical SaaS services:

Use the top popular publicly available reference SDK client libraries as compatibility targets, with the goal always being 100% compatibility.

You've also zeroed in on how challenging this was: I started this back in August 2025 (as one of many projects, at any time we're each juggling 3-8 projects) with only Sonnet 3.5. Much of the work was still very unglamorous, but feasible. Especially Slack, in some ways Slack was more challenging to get right than all of G-Suite (!).

Now I'm part way through reimplementing the entire DTU in Rust (v1 was in Go) and with gpt-5.2 for planning and gpt-5.3-codex for execution it's significantly less human effort.

IMO the most novel part to this story is Navan's Attractor and corresponding NLSpec. Feed in a good Definition-of-Done and it'll bounce around between nodes until it gets it right. There are already several working implementations in less than 24 hours since it was released, one of which is even open source [0].

[0] https://github.com/danshapiro/kilroy

Yes, Claude code.

Can this work for Claude? I think it might be raw API only.

(StrongDM AI team member here)

This is great feedback, appreciate you taking the time to post it. I will set some agents loose on optimization / purification passes over CXDB and see which of these gaps they are able to discover and address.

We only chose to open source this over the past few days so it hasn't received the full potential of technical optimization and correction. Human expertise can currently beat the models in general, though the gap seems to be shrinking with each new provider release.

I'm one of the StrongDM trio behind this tenet. The core claim is simple: it's easy to spend $1k/day on tokens, but hard (even with three people) to do it in a way that stays reliably productive.

https://jaytaylor.com (personal site)

All of my web properties have been ad-free since the beginning, going on 25 years. Cheers.

(Co-creator here) This is one of the use cases for Leash.

https://github.com/strongdm/leash

Check it out, feedback is welcome!

Previously posted description: https://news.ycombinator.com/item?id=45883210

Leash does it via eBPF today. Are you open to a collab?

This is a really neat project .

At my company (StrongDM) we recently open-sourced a tool in this space called Leash: https://github.com/strongdm/leash

By default it runs in docker, and also includes an extra sophisticated macOS-native --darwin mode which goes beyond the capabilities and guarantees of the likes of sandbox-exe, bubblewrap, and in some ways docker. Leash provides visibility into and control over every command and network request attempted by the coder agent. Would appreciate any feedback, and will try to get in touch with the author (Gordon).

Now I'll definitely look into automatically supporting pass-through auth for at least gh cli in Leash - always looking for what folks will find useful.

Have you seen Leash?

https://github.com/strongdm/leash

It even has a --darwin macOS-native mode which goes beyond the capabilities and guarantees of sandbox-exec and bubblewrap.

Full-disclosure: I am one of the authors.

https://jaytaylor.github.io/hn-live2

Enjoy!

X-Mouse Button Control (XMBC for short) is a handy Windows app to override mouse buttons to do arbitrary other actions on a program/App -specific basis.

https://www.highrez.co.uk/downloads/XMouseButtonControl.htm

However the docs (which are excellent!) were published by the developer as PDF-only, so I did a nice transform to HTML and posted it on my personal website. I will do my best to host it until I'm dead, and also submitted it to TIA:

https://www.highrez.co.uk/downloads/X-Mouse%20Button%20Contr...

https://jaytaylor.com/x-mouse-button-docs/

Forever TIA link: https://web.archive.org/web/20240825203006/https://jaytaylor...

Cheers,

Jay

Years ago I made a Go library called `html2text' just for this:

https://github.com/jaytaylor/html2text/

https://jaytaylor.com/html2text

It takes HTML as input and generates markdown-esque plaintext, with the main focus being to make the plaintext version easy and pleasant to read for human beings. Then using MIME types*, you transmit both the rich html version alongside the generated text/plain version.

This is cool because it makes it easy to respect both rich clients (like Gmail et. al.) as well as command-line or other clients which work better with simple text.

Hope this helps folks have the best of both worlds! :) cheers

* n.b. To ensure this works properly, be sure to use the right MIME headers:

https://stackoverflow.com/questions/3902455/mail-multipart-a...

Hygroscopic, an interesting new word to me! Thank you :)

hy·gro·scop·ic

adjective

(of a substance) tending to absorb moisture from the air. relating to humidity or its measurement.

I didn't know the word internecine, it's actually really useful and relevant in many situations, thank you!

internecine, adj.:

destructive to both sides in a conflict.

Underscores aren't technically valid in URLs or domain names ;D

That minor implementation detail aside... You make a good point. Perhaps MD5 or SHA256 hashes will become a last resort for domain names? Haha, no.

I’ve often thought about getting together with some friends to pay into a fund to house our websites after we die. I don’t think setting that up would be too hard — the math around insurance policies of this sort is quite simple — I mostly haven’t tried to set something like this up just since it’s a pretty morbid ask. But, if you’d be interested, maybe reach out to me?

Our ghosts could live forever, if we help each other.

I love this idea and would gladly assist in the effort, let's set it up :)

The Klingons were hella cool! Wish I could have appreciated it more as a kid, but at the time (early 90s) I didn't even know what I was looking at or how special it was :D

Tangentially related:

https://news.ycombinator.com/item?id=28489791 - Checkboxland

https://news.ycombinator.com/item?id=28826018 - I keep making things out of checkboxes

It hasn't been cooperative for a few versions now, the scheduler became preemptive in 1.14. And before that there were yield points at every function prolog (as well as all IO primitives) so there were relatively few situations where cooperation was necessary.

Since co-op was most unnecessary, do you know why it was changed to preemptive or what the specific cases were that are resolved with preemptive scheduling?

Litestream can ensure a pretty decent level of durability, for a ramdisk anyway.

Suitability depends on what the requirements are.

Also posted yesterday: https://news.ycombinator.com/item?id=31252441

No discussion as of yet, but I favorited it because I plan to try it out in the near future.

Thank you binwiderhier for doing all this hard work, your drive is impressive!

Is your development progress taking place in the open? (e.g. GitHub or somewhere similar)

It sounds like a cool project and I'd love to see it! And even have the option to open a PR and help ;)

Also Oracle OCI has OKE, which is Oracle Kubernetes Engine. It works nicely and the quality of service has been very good in my experience over the past four years.

Disclaimer: I currently work at Oracle.

If there was a way to subscribe to email notifications whenever you post, I totally would!

In case it's helpful as a reference, the righto.com guy has a nice setup.

Is there an RSS feed for your articles?

Which filesystems support this degree of integrity checking? Presumably ZFS, but what about EXT4/3, ReiserFS, BTRFS, ZFS, NTFS, and FAT32?

It would be wonderful if they all have the feature, but I thought only ZFS was really that paranoid.

If anyone else is wondering what is a "DRC problem":

Design Rule Checking (DRC) is a process used to identify errors and mismatches such as spacing & trace widths in a PCB design/layout.