Talderigi

Curious how the semantic caching layer works.. are you embedding requests on the gateway side and doing a vector similarity lookup before proxying? And if so, how do you handle cache invalidation when the underlying model changes or gets updated?

feels like people are arguing the wrong axis tbh

- it’s not open vs closed anymore, it’s more like bug finding going a few devs poking around to basically infinite parallel scanners

- so now you don’t get a couple of thoughtful reports, you get a many edge cases and half-real junk. fixing capacity didn’t change though

- closing the repo doesn’t really save you, it just switches from white-box to black-box… and that’s getting pretty damn good anyway

real problem is: vuln discovery scaled, patching didn’t. now everything is a backlog game

If you map Rust threads to warps, aren’t we basically turning the GPU into a very expensive CPU?

Is Servo production-ready enough to replace or embed alongside engines like WebKit or Blink?

rust fixed memory safety but left build-time trust wide open. What’s the realistic path to fixing this? sandboxed builds by default, or stricter provenance (sigstore-style) or what?

fully agree, doesn’t really feel like they’re reacting to the same problem they’re describing

We built systems we don’t fully understand, so naturally the next step is… immunity

open source but the off switch is centralized