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?
While I’m receptive to the fact that RAGs have performance limitations, and that graph database-based solutions may avoid hallucinations, wouldn’t your rhetorical position be best served by offering a trial portal for users to upload their own document corpora and see for themselves that prompts to Stardog never result in hallucinations? Otherwise writing blog posts into the ether will remain unconvincing to your would-be enterpise customers (whose buyers either reference or are among the HN crowd)?
I must say this is amazing. The psychology and manipulation makes me realize how poor I am regarding trust even when the other side is pushing for some unconfirmed equilibrium.
In the game I acknowledge that I was aligned to the "Simpleton" strategy (before it was outlined). Looks like simpleton might actually be applicable in a more general sense too which is a little disheartening.
I now want to hear more as to why Defold now has a clojure repl! I noticed some musings around some native bindings in gh issues which is "interesting" but I'm not quite getting it. I guess off to the forums I go!
Which also points to landlock-make[0] or vice-versa (the original project that made me aware of the kernel functionality (although didn't realize it also isolated network which is great).
Italo Calvino was noted as being of great inspiration to Jonathan Blow (as a relative point of interest on the OP's question)
I think during one of the Braid 20th anniversary podcasts[0] he talks to it which I loved listing to (from a historic viewpoint; well moreso than a game dev/design)
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.