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.

I agree! Comes with the territory of a compiled language I suppose?

I haven't given this much thought (I also just started with golang last year) but I'm assuming the only real path here is to provide extension SDKs in Lua or other languages whose interpreters have been implemented in go.

I think that's what grafana's k6 [1] does with a JS interpreter

[1] https://github.com/grafana/k6

Or fnm! I use it and it's lives up to the name (it's much faster)

It's competitive!

Good enough to show competence, and instill confidence in the team/company. Later releases can be more efficient.

I think it's a great release with that framing.

Why did you create it? What were you looking to solve address?

What limitations of shadown dom are you referring to? I use Lit (just a bit) and I'm not familiar with any limitations

Oops! I admit I don't have much knowledge on hashing algos. I thought it was a shorthand

I personally have been using `go-libfossil` in a project! It's got some sharp edges but insanely useful in avoiding CGO and using fossil at the same time

Agreed! This isn't a tech dig at all.

To me it's more of a reality of creating a tool with a huge active community and a community of contributors and creating a tool with a small team and small community.

Hmm probably nothing architecture wise. It's probably just the fact that fossil is developed by way fewer devs.

From the skim I read of this article it seems both projects arrived at the same solution: support both but make SHA-256 the default.

One of my favorite fun facts about Fossil SCM (another source control by the devs of sqlite) is that they patched their use of SHA1 6 days after the shattered attack was published:

"Both Fossil and Git started out using only SHA1 hashes. But when the SHAttered attack against SHA1 was published on 2017-02-23, the need to migrate to a stronger hash algorithm was recognized. Fossil added the ability to use SHA3-256 as an alternative on 2017-03-01 (six days after the SHAttered attack was first published). SHA3-256 is now the default for all new repositories and check-ins in Fossil, though older check-ins that occurred prior to SHAttered can still use their original SHA1 hash. Hence, no repositories had to be rebuilt and no hyperlinks were broken."

https://fossil-scm.org/home/doc/trunk/www/hundredandone.md

To me it's so interesting watching in realtime Git is still battling with this decision and for Fossil it was just another week of development.

That whole page is fun to read. Another fun fact somewhere else in the docs is that Fossil uses a grow-only set to store commits. They came up with this scheme some years before it was formalized by CRDTs!

Are you ready to call this race 5 years in? I'm waiting another 15 years and at least one or two new LLM architectures.

Wow I didn't realize it was Brendan Gregg doing the screaming. What a legend!

This is a great example! Thank you

I think you're right that it's a matter of taste and that the intent is better represented by reladraw.

If I can point some personal downsides of pikchr is that there's no loops and when using macros you can't use parameters to create object labels.

For example, Triangle$1: line...

Just some thoughts in case you're looking for future inspiration for the language

Can you share an example?

I've been playing with pikchr quite a bit and it has containers and you can specify links relative to the container. I can picture (pun not intended) your counter-example

Have you tried goyek? It's built exactly for this kind of use case. I find the API great but I'm also a newbie

https://github.com/goyek/goyek