gandreani

Thanks for commenting anyways! It's helpful feedback for me

I was struggling with the audience I targeted.

I think I started writing with a hackernews and LinkedIn crowd in mind and then just finished writing it with hn types in mind.

No it's no inscrutable but for the average person it's just a spaghetti wall of text

Saying the GPU is doing thinking but the model is not is a WILD take.

What is your definition of thinking?

This is a very nice use of eBPF and probably close to the imagined scenario the kernel developers proposed for this.

eBPF has a terrible name but it's absolutely wonderful tech. If you're running a database SaaS you can implement eBPF filters to do the accounting for billing based usage, regardless of which database you use!

To me that's irrefutable evidence that it's really well designed

I find it kind of amusing to consider that the go team didn't commit to implement this automatic connection re-use until they probably encountered in the wild the horrible but correct third iteration of drainAndCloseBody.

1. Suggest drainAndCloseBody // Team: this is reasonable

2. Implement drainAndCloseBodyWithTimer // Team: no problems here

3. then drainAsyncAndCloseBodyWithTimer // Team: a bit wordy but no problem here

4. Someone at google uses 3. with an http/2 connection // Team: this is where we draw the line?

I sympathize with the struggle of following golang's mission to be simple when you consider this common but tricky edge case. Iteration 3 makes sense but by gosh is it ugly ha.

Oof, that is an edge case I wasn't aware of at all. Hard to know where it's documented since it's an integration of both those packages

Thanks for writing this library! It's great. I've used it a couple of times and never had an issue

What do you mean 60k complexity?

Curious about this implementation. How does the vector search work with a versioned code base?

If I'm on commit A, then save the work and now I'm on commit B, how does cross-search ensure it doesn't return results for code JUST in commit A (i.e. code that is no longer in the codebase).

It's easy to be dismissive of this guy's hubris. Already have a lot of comments in that regard!

I think it perfectly illustrates that even though an agent can give you the abilities, it's still up to the driver to make decisions.

In this case the CEO could have consulted someone with your expertise. Same ability, but vastly different experience.

"Both the plugin and the main application must be compiled with the same Go toolchain version, build tags, relevant build flags, environment settings, and common dependency source on the same platform."

Yikes that's a hard set of requirements. Makes sense but I can already see a ton of headaches with that

I agree! I can't comment on the design of the SDKs but from the looks of it this is a great option to integrate into agent harnesses/pipelines.

The "audit" and "debug" mode are specially useful. I use bubblewrap and using a new harness with it is usually a couple of rounds of wack-a-mole with strace to figure out all the harnesses dependencies.