Rendered at 10:55:36 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
chanux 2 hours ago [-]
It sounds like the solution simplifies something but I could not figure out how or what.
bawolff 4 hours ago [-]
I understand that you can do this, but I'm not sure i understand the rationale. I can't imagine that this is a hot enough path that this makes sense from a performance perspective, so why? What's the benefit?
Naively the thing this is replacing sounds like a much better solution than the replacement is.
therein 2 hours ago [-]
Pretty strange thing to do.
That aside, definitely AI written. The cadence is a dead giveaway.
stevekemp 2 hours ago [-]
Very much so.
Though weirdly there's a part in the middle " 8125 is contentionally what statsd used" which should obviously have used "conventionally", so who knows which parts were written and which prompted for.
I'm reaching a point now where I'd really just rather see the prompts than these kinds of posts.
lloydatkinson 13 minutes ago [-]
> the way apps have done since Etsy taught everyone to in 2011.
What in the slop is this?
theamk 2 days ago [-]
> We replaced the listener with an eBPF program that watches port 8125 at the traffic control layer of every interface, and a JavaScript decoder that turns the lines into Prometheus families.
this is insane! Why on earth would one to replace a short, simple, highly debugable program with this crazy combination. Why would you trade a simple socket(2) call which shows up in ss, netstat, strace etc.. with something that opaque? Especially given the bandwidth is minuscule and the destination is already localhost.
cookiengineer 2 hours ago [-]
Web developers make web developer choices while vibe coding.
Your past experience limits your thinking, especially in agentic environments.
But I suppose their whole business model is built upon that, given that yeet is a bun/node/deno library with bpf support.
r3tr0 1 hours ago [-]
founder here. we are not a bun/node/deno library.
we embed V8 directly and just point it at bpf
r3tr0 1 hours ago [-]
the choice of javascript was very intentional.
it has some really nice properties for dynamically instrumenting the OS.
and provides lightweight isolation for agents to control probes and do deep packet analysis.
lloydatkinson 12 minutes ago [-]
Which popular systems if any use this? So I can avoid it.
tucnak 2 hours ago [-]
Maybe they wanted to play a bit with eBPF... The only reasonable conclusion. Wait till they go beyond localhost and discover XDP!
r3tr0 1 hours ago [-]
haha we got xdp, tcx, BPF_MAP_TYPE_ARENA you name it ;)
Naively the thing this is replacing sounds like a much better solution than the replacement is.
Though weirdly there's a part in the middle " 8125 is contentionally what statsd used" which should obviously have used "conventionally", so who knows which parts were written and which prompted for.
I'm reaching a point now where I'd really just rather see the prompts than these kinds of posts.
What in the slop is this?
this is insane! Why on earth would one to replace a short, simple, highly debugable program with this crazy combination. Why would you trade a simple socket(2) call which shows up in ss, netstat, strace etc.. with something that opaque? Especially given the bandwidth is minuscule and the destination is already localhost.
Your past experience limits your thinking, especially in agentic environments.
But I suppose their whole business model is built upon that, given that yeet is a bun/node/deno library with bpf support.
we embed V8 directly and just point it at bpf
it has some really nice properties for dynamically instrumenting the OS.
and provides lightweight isolation for agents to control probes and do deep packet analysis.
check the docs.
https://yeet.cx/docs