willk retweeted
Today, I'm thrilled to announce Pramaana's $27M seed, led by @khoslaventures.
The foundational domains that hold the world together: tax, law, finance, healthcare; all run on certainty. Probabilistic AI can't give them that. We’ve been asked to accept wrong answers with AI as ‘hallucinations’, while in traditional software terms, it’s just a bug. And a wrong answer in such mission-critical domains is more than just a bug, it's a liability that could have catastrophic impact.
We built Pramaana to deliver a 100% trustable experience to the domains that run on certainty: AI that is provably correct, not probabilistically correct. We turn statute and regulation into machine-verifiable code, so every output ships with mathematical proof of correctness. Our mission is to make AI take ownership of it’s work.
Pramaana in Sanskrit stands for “means of valid knowledge”, and we’re going to achieve that by formalizing the world’s knowledge.
willk retweeted
📢 🪂 𝐎𝐖𝐍 𝐓𝐇𝐄 𝐅𝐈𝐑𝐒𝐓 𝐄𝐕𝐄𝐑 𝐋𝐎𝐘𝐀𝐋 𝐀𝐈
In the coming days we will release Dobby, the first ever Loyal AI model. Participate in our first ever 𝐅𝐢𝐧𝐠𝐞𝐫𝐩𝐫𝐢𝐧𝐭𝐢𝐧𝐠 𝐂𝐚𝐦𝐩𝐚𝐢𝐠𝐧 to earn ownership of Dobby.
Pre-register: register.sentient.xyz/
willk retweeted
In React 18, two components that are siblings to each other can suspend together within the same Suspense Boundary because React keeps (pre-)rendering siblings even if one component suspends. So this works:
<Suspense fallback="...">
<RepoData repo="react">
<RepoData repo="react-dom">
</Suspense>
Both components have a suspending fetch inside, both will fetch in parallel and will be "revealed" together because they are in the same boundary.
In React 19, this will be a request waterfall: When the first component suspends, the second one never gets to render, so the fetch inside of it won't be able to start.
The argument is that rendering the second component is not necessary because it will be replaced with the fallback anyway, and with this, they can render the fallback "faster" (I guess we are talking fractions of ms here for most apps. Rendering is supposed to be fast, right?).
So if the second component were to trigger a fetch well then bad luck, better move your fetches to start higher up the tree, in a route loader, or in a server component.
willk retweeted
dataclient.io/blog/2024/04/0…
Full safe store access using schemas 🔥
willk retweeted
resthooks.io/blog/2022/12/19… Rest Hooks 7 is here! @nextjs SSR integration, better @reactnative support and more!
willk retweeted
Rest Hooks 6.5 and @rest-hooks/6.1 released!
resthooks.io/blog/2022/11/09…
willk retweeted
TypeScript inferred from /user/:id template paths resthooks.io/blog/2022/10/23…
willk retweeted
Today, we announce the launch of the Coinbase Prime Approvals app for institutional investors!
🤳The perfect mobile accessory to your Coinbase Prime experience, access portfolios and approve consensus activities on the go.
Get started → apps.apple.com/us/app/coinba…
willk retweeted
we need to stop celebrating the pilgrims coming to america (problematic, complicated) and start celebrating this (consistently the best)
willk retweeted
They say you have to set your clocks back on Sunday but I’m going to do my own research.
