Wow thanks for pointing this out! This is actually what I was hoping would happen when the deepspec stuff dropped! And having zlab create these confirms my bias that I think open models are the way.
Yeah I'm with you, this feels like a case for assertions & not a new core feature. Perhaps I'm missing something because it was promoted by Michael Fogus and has been ratified by those who would know (Alex I'm assuming). To me it doesn't pass the test of necessity as something needed at the core but at least it feels somewhat ideomatic.
This is a pretty harsh critique, while I see the agent related markdown the application seems measured and well applied. Hardly seems like slop; it's might be a one man show+ai agent but the direction and project composition feel like it's something that's logical and manageable.
I personally like the idea even as a p.o.c (inline with bellards work). I'd like to see how nostr & cloudflare workers providing out of band ops on what is effectively a container per tab.
I really do love what kdb is doing but I think maybe they lost too much momentum (and confidence) when back flipping on previous agreements for the community editions. (Which I don't think they will again with the kdb-x releases as they have a good balance this time) It would have been nice to see torqx just work (tm)
Redacting "I noticed that a kernel level impl is only 9000 loc (shallow dive
https://lwn.net/Articles/1029851/). As it doesn't fully implement the feature set.
Also I noticed that Plan 9's IL protocol (avoids head of line because the type of messaging it's used for) another point pointed out in the x comments.
I wonder if he's focusing on consumer distributed AI inference (due to quic being browser supported) or maybe just a comment on the protocol in general.
This is the kind of clojure port that I always was looking for. Mostly because I thought go's core library and channels abstractions hits a simpler/nicer base API which would with the core & async apis (not to mention scratches my big beautiful binary itch)
Thanks for your work will definitely check it out again once I get over renewed love for cpp (26)
Edit how did glojure go under my radar also a great project from the looks
Ah this reminds me of my favorite stack which I never got to actually work with; luvit.io (libuv with luajit; both hot items at the time).
I hope this becomes a thing, typing in lua might make it easier to scale for teams (which I think is always an issue with dynamic language)
I really should check up on what Mr Caswell is up to. He was quite inspiring with both his diy home improvements as well as activity in the development space.
While I haven't read all the posts here I was wondering if anyone also noticed a 10% usage before their most recent weeks usage even started? (Specifically over 2026-03-27/28) I was seeing weird service outages over this time too. I suspect they're not being 100% truthful with how they are recording usage (feels like they had an agent run a backfill approximation). So they blur it with weekends rates etc.
Anyways I don't have the knowledge as to how to audit this (claud pro) to confirm what feels like an onboard at any cost business behavior.
Is anyone currently auditing through openrouter/litellm and seeing any poor correlation to the session/weekly limit?
Sorry, I did compose it from my phone and wasn't clear. I realize the article talks to the Maven tooling I was talking to it's data aggregation and modeling suite more generally. (And obviously would have been used as part of the Iranian engagement. The "if at all" statement was meant to be "tongue in cheek" given the current mess being reported)
I'm curious as to how Palantir has been used during the war or Iran (if at all or does it suffer from subjective bias). I know there were larger movements at play on a political level here but I'm becoming concerned about how much one "thought group" (in private corps) is having on the world's largest war machine. might be dulling critical thinking.
It seems like a real problem for me. Probably because I'm not overly inspired to pay for a Claude x5 subscription and really hate the session restrictions (esp when weekly expend at the end of the week can't be utilized due to session restrictions) on a standard pro model. Most of my tasks are basically using superpowers and I find I get about 30-90m of usage per session before I run out of tokens (resets about every 4 hours after which I generally don't get back to until the next day (my weekly usage is about 50% so lots of wastage due to bad scheduling). A tool like this could add better afk like agent interoperability through batching etc as a one tool fits all like scenario.
If this gets its foot in the door/market-share there is plenty of runway here for adding more optimized agent utilization and adding value for users.
I used to work for a human that did this (sits mostly on the classical therapeutics side). He actually started a business where he was reviewing and auditing the submission processes outlining approvals but he had been around the game enough to know where the next submission would put them in the approvals process for a number of agencies.
Looks like he's still on top of everything given the most recent blog post is from 6/2/2026.
I believe the insights here could be useful given he has sense of when the penultimate submission has occured (but I'm not entirely sure what that is on a % basis nor as a basis for if the stock of the company reacts)
Yeah, but it's specifically testing things that implement against a posix API (because generally that's what "native" apis do (omiting libc and other os specific foundation libraries that are pulled in at runtime or otherwise) I would suspect that if the applications that linked against some wasi like runtime it might be a better metric (native wasi as a lib/vs a was runtime that also links) mind you that still wouldn't help the browser runtime... But would be a better metric for wasm (to native) performance comaparison.
But as already mentioned we have gone through this all before. Maybe we'll see wasm bytecodes pushed through silicon like we did the Jvm... Although perhaps this time it might stick or move up into server hardware (which might have happened, but I only recall embedded devices supporting hardware level Jvm bytecodes).
In short the web browser bit is omitted from the title.
Perhaps if a supply chain attack is your largest concern then using some well vetted system like wolfi is more up your alley. (See some of their related repos on GitHub https://github.com/projectbluefin - I've been following the development of it and currently it still under development.)
Again "vetting" is a source of contention here as I'm not sure how the quality of official rpm sources compare to those outlined in an sbom
Yeah, but there is something else here too... I used cachy for a heartbeat and it advertises the same benefits; it just felt slower (notably on boot) Maybe it was just all the graphical load screens.
There's something clear had that made it feel modern, familiar and boring (which might not be for everyone) 90% of my tasks were in vscode devcontainers so kept things simple and out of the system for the most part.
I do love the warnings here... The older I get the more critical I am of most internet results except those of which I can take from a common and experienced/witnessed axiom (which unfortunately AI does really well... At least entrusting me to said point). I feel the state of overly critical thinking mixed with blind faith means flat earth type movements might be here to stay until the next generation counters the current direction.
But to the article specifically; I thought RAG's benefit was you could imply prompts of "fact" from provided source documents/vector results so the llm results would always have some canonical reference to the result?
I think this is the first time I've seen this hit #1 which is nice