Comments on How (and why) we rewrote our production C++ frontend infrastructure in Rust

By: Douglas Muth

2026-05-14T02:31:59Z

It’s always good to read about a successful project like this, and I’m glad that after all these years, y’all are still building new things.

I can’t wait to see what features are rolled out for the service next!

By: Onion

2026-05-07T01:03:45Z

Well that explains why I have to learn a bajillion new reasons “why” something exists when I try to learn something new with this infra. But constraints force creativity, and creativity forces learning. So at the end of the day we should all be grateful when things cause friction and force us to learn new paths. Thanks, homie.

By: bmh

2026-04-29T19:48:34Z

Great work! Happy to not have noticed. 🙂

I think the biggest problem with AI vibe coding is delegation: it fragments cognition across multiple entities (you and the AI), which limits confidence in correctness. This can happen with delegating to a person, too, but it’s especially problematic with AI because of scale. The point is when systems are critical, one single mind should be both in charge and deep in the weeds.

Glad to know this wasn’t vibe-coded. 🙂

By: jdw

2026-04-28T01:39:32Z

In reply to Nick Levinson.

All other problems with AI aside, just the idea of vibe coding a project like that makes me nauseous. -jdw

By: Nick Levinson

2026-04-25T20:09:37Z

Sounds terrific. This description is why I don’t think AI is ready for prime time. I doubt anyone should’ve trusted AI to generate all that, including the testing, without some future major failure.

By: Tim McCormack

2026-04-17T21:44:44Z

Last year I rewrote a small but excitingly dangerous web service and we did something similar to your proxy testing, although in our case the switch, comparison, and telemetry code was built directly into the client.

I can confirm that you can find some really weird bugs (including existing behavior) that way. 🙂 Can’t recommend it enough.