It’s a great piece of software. I set it up in a Docker container, and have a few of their CI runners on a couple machines I own. Great experience so far.
Zed is fantastic. Just dipping my toes in agentic AI, but I was able to fix a failing test I spent maybe 15 minutes trying to untangle in a couple minutes with Zed. (It did proceed to break other tests in that file though, but I quickly reverted that.)
It is also BYOA or you can buy a subscription from Zed themselves and help them out. I currently use it with my free Copilot+ subscription (GitHub hands it out to pretty much any free/open source dev).
I'm going to say "no". In her example she mentions that the problem she's trying to solve is that flowcharts [1] need to be 3D to model multiple systems and components operating in parallel, but that's just trying to push a single-system tool beyond it's usefulness. Trying to model multiple systems like that would lead to an explosion in the number of transitions very quickly.
The closest we have nowadays to her "3D flowcharts" idea would be UML in general [2] and Orthogonal State Machines [3] in particular, but I think that what her problem really needed was better encapsulation and interfaces between systems.
Yup - thats what an AI vector DB is all about - matrices.
--
EDIT: @-probably_wrong
You have to think that she also has to put things into the minds of others who dont have here prescient forethought of systems.
Listen to all she says about "systems of computers" where "you need a computer to run all these other computers" and that you have ~160KB over head to run a 32KB program... andn how she breaks down all the constituents in a cluster, down to security auth...
And she tells you to buy a Scientific Molocule Model set to be able to design computer systems in 3d.
I agree that she's right regarding how distributed systems will eventually work. My disagreement is not with the "what" nor the "why", but rather with the "how". If a "better Molecule Kit" were the solution then I think we would have built one today in VR.
IMO the fundamental problem is that visualizing complex systems fails because the result is either too cumbersome to be useful or too simplified. UML tried to solve that issue (in 2D) by allowing you to go into more/less detail as you need it, and yet its adoption in modern software development is uneven at best. And there's a reason why we use flowcharts mostly for beginner's problems.
The actual solution, I believe, was getting away from visualizations by making robust software (well...) with clear interfaces to abstract the complexity away. Reaching this conclusion took a lot of work by plenty of brilliant minds, so I'm not faulting her for not being that accurate in that particular prediction.
NVIDIA named one of their chip platforms after her.
I mean, at the time that she was saying this, you couldnt fill a Trump Rally with as many people on the planet at the time knew the future of compute the way she did.
Before looking into the actual bitcoin block structure, and realizing this wasn't possible, I thought that maybe hashes were a hash of a hash.
A hash is essentially just some random bytes, there is a small chance that the first hash bytes would randomly all be printable characters that fit the submission format, given that the bitcoin network has already done most of the work finding the small hashes, scanning through the blockchain trying to find a hash with a plaintext that fits the submission criteria, should be much less work.
They are hashes of hashes, and in fact I already did scan all* the blocks to check if any of them meet the constraints, just in case (they don't, and it would be extremely unlikely but not entirely out of the question).
*as of a year or so ago (my archive is stale and I'm too lazy to update it)
No, you're looking for a suitable hash but not an exact match to anything. Some of the hashes are premined. But you do need the hash input to fit a specific format. That's still more likely and more accessible than a collision (I'm sure scanning all the available values is computable in a relatively shorter time than finding arbitrary collisions with a specific hash).
