Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Cap'n-rs – Rust implementation of Cloudflare's Cap'n Web protocol

github.com

Post reply on HN
Print view View original

31–36 of 36 posts

Re: Show HN: Cap'n-rs – Rust implementation of Cloudflare's Cap'n Web protocol

#31

Post by brian_meek »

adrian17 wrote: post #7
IshKebab wrote: post #2

I would recommend not having an AI write your README. Even if you didn't use AI for coding at all and the code works perfectly, it really doesn't inspire confidence.

The commit names look very weird too, feel more like marketing speak: > BREAKTHROUGH: Fix critical ID mismatch in Cap'n Web protocol > TIER 3 ULTIMATE: Extreme Stress Tests & Advanced Capability Composition > Achieve Cap'n Web protocol mastery with perfect capability composition (note: this exact commit name is repeated another time) The commit descriptions are even worse. If they’re so blatantly not written for anyo…

OP here. :-) (feel like I should put an emoji here). My focus as I "built" this was getting to a correct implementation, and putting in place guards and context to achieve that. As I moved through the process I added more and more ways to eval progress toward that. An area I didn't invest any of my effort in was commit messages, and some of them caused me to spit take as I saw them go by. I think this is something that can definitely be improved, and this conversation is fuel for thought on how to do this.

Re: Show HN: Cap'n-rs – Rust implementation of Cloudflare's Cap'n Web protocol

#32

Post by brian_meek »

nextaccountic wrote: post #16
mort96 wrote: post #14

Earlier quoted context omitted.

To be honest, I don't really understand the point of Cap'n Web.. it's a slightly better JSON-RPC I guess? I'm a fan of Cap'n Proto, but I don't understand how Cap'n Web is in any way related to it nor what makes it a big deal.

The selling point is promise pipelining, being able to do many chained operations with a single api call This includes the freaky way they found to make this work with map

OP here, and yes, the chained operations are excellent. Having built this, and now using it some pet projects, that is the part I'm finding valuable.

Re: Show HN: Cap'n-rs – Rust implementation of Cloudflare's Cap'n Web protocol

#33

Post by brian_meek »

kentonv wrote: post #21

Hey it's super-cool that you've implemented Cap'n Web in Rust! Nice! But would you mind renaming the packages to make it clear they aren't official, before too many people depend on them? Prefix with your name or "currentspace" or something? I'd just hate for it to be a big mess later if we ever decide to release an official implementation (and if it's not based on yours).

Thanks for looking, and yes, I can rename it. Will do today. Also, thanks for the excellent protocol. In this entire "effort", I only found one ambiguity in it (and reported it in your repo). Everything about it was well defined and succinct. The pipelining is really useful.

Re: Show HN: Cap'n-rs – Rust implementation of Cloudflare's Cap'n Web protocol

#34

Post by dlahoda »

brian_meek wrote: post #26

OP here. Thanks for all the thoughtful feedback, I really appreciate it. I mentioned in the README that I leaned heavily on Claude Opus for the port. One of the biggest challenges was tamping down its default “everything is production-ready in a week” optimism. That said, I also discovered along the way which guardrails worked and which didn’t for guiding it toward a compliant implementation. It was good learning, an…

did you use lates claude release? did you ask codex to review and bug fix? what wat time spent promting, manual fixes and waiting for agent to finish work?

Re: Show HN: Cap'n-rs – Rust implementation of Cloudflare's Cap'n Web protocol

#35

Post by mort96 »

brian_meek wrote: post #29
mort96 wrote: post #15

Earlier quoted context omitted.

The two big signifiers that something is "ready for production use" are: 1) it has been successfully been used in production at some scale for a while, and 2) it has some commitment to API stability. A 1 week old project on version "0.1.0" is neither, whether vibe-coded or not.

OP here. I frankly stopped trying to add evals for the "ready for production" happiness Claude is trained to produce. I agree, not ready for production. I did though put a intention and effort into guarding against slop in implementation and tests. Sure I can still find it, but I believe the current state is solid enough to build on, and I will be doing so for some pet projects. I'll let you know what I find when usi…

What do you mean by this?

> I frankly stopped trying to add evals for the "ready for production" happiness Claude is trained to produce.

It's your readme, no? Does Claude just go in and change it behind your back..? What's going on here, are you not in control of what you push to git?

Moreover, what thought process makes you okay with lying in your readme just because the robot wanted you to?

Re: Show HN: Cap'n-rs – Rust implementation of Cloudflare's Cap'n Web protocol

#36

Post by typpilol »

sandblast wrote: post #6
typpilol wrote: post #5

Earlier quoted context omitted.

Makes me sad because I used to put a lot of effort into my readmes. Not insane amount of emojis but some and actually useful badges but not overkill. But in the end they always had nicely structured layouts etc.. I feel like I have to make mine sloppier now to pass the AI smell test

Maybe it was also your style that the LLMs learned from (and then pushed more towards the extreme). Oh the irony.

That would be even more sad
Post reply on HN