I can relate to the tilting you're on, but try to consider the good that can come from this age, where such a tool might not have been built otherwise. It's also BSD/GPL license.

As an aside, I've been vibe-cooking for a few months on a personal project that's accomplished something lovely. For me. I sometimes wonder if I should give it away much like this project. But public reactions like yours temper the thought.

Hey, I'm the founder of yeet.

This tool was built on top of our engine: yeetd.

We put a lot of work into abstracting BPF into a JavaScript framework to give builders, human or agentic, the ability to use complex kernel primitives with a familiar programming model to build production grade, scalable infrastructure tools.

Our hope is that everyone here will soon be able to build their own tools on-demand, versus buying them.

We separate a lot of the data layer code from the presentation-level code, to make them re-usable and keep the test surface on the actual data's accuracy manageable across all the random edge cases that arise across CPU architectures, kernel versions, and environments like AWS ECS network namespace voo-doo.

It seems like a tool built for this bigger project[1] which actually looks kind of creative and cool.

[1] https://yeet.cx/

> Thank you, but I won't even consider a yet another AI/LLM slop which will not be maintained in a few months, nor anyone will ever invest their life time into, too.

This applied to most of my side projects before AI. Most of them I would never touch again.

Thanks to AI I'm working on them way more, and at a much higher level of engineering standards (especially the recent models are voluntarily adding tests, looking for bugs etc.).

(Well, except for the part about barely reading the code, but I said higher, not high!)

Also I realized the other day that I already reached the point where I don't understand my own code, several years before involving AI in the process!

I don't know if I'm an outlier but I thought that was pretty funny.

[dead]