Robert Mustacchi

Exactly. It's all the EDA folks. It's all the EDA folks who are like.

Exactly. It's all the EDA folks. It's all the EDA folks who are like.

Yeah.

Yeah.

Yeah.

Yeah.

That's for Sony and Microsoft to take up.

That's for Sony and Microsoft to take up.

How does it feel to be doing this from the morning?

If you spent any time in a European Airbnb, regardless of the country, you know that they always have a large canvas of a black and white scene of London with a colorized red bus. So I think that's the first clue that this is not actually Italy.

There was an initial version that already existed when I joined. And it was just a list of kind of RFDs that were rendered. I think... I think at that point, a lot of people were looking at RFTs directly on GitHub. I guess due to the deficiencies of the site. And then I don't remember exactly when we kind of relaunched sort of the version that we have now. We kind of were built upon it since.

But then we kind of incrementally added things like the full text search. That was a huge pain point for me. I forgot what kind of command it was. There was some kind of grep thing, which would take... would take minutes to search the. It was a long time. It wasn't a great process. And now we have full text search.

We're using some library that indexes all the RFDs and searches, which I think is a good, that's super useful. I can, to your point earlier, we're sort of at an inflection point where there's so much in there that even full-text search doesn't necessarily get you everything that you need. Someone's already mentioned LLM, so I think I'm free to do without kind of...

Yeah, you don't have to feel like you're breaking the schedule. I'm not being accused of a shill, but I think there's, on the roadmap, there's, I think, there's room for something that kind of summarizes all the RFDs and at the very least tells you where to look. And let's say you're joining at Oxide.

There are a bunch of RFDs that everyone should read, but for most people, there's a smaller group which are kind of really pertinent to their work.

And I think that we can use something like that to generate reading lists for people that, that join and they can, they can kind of, they don't feel like they're just losing their mind, like drinking from the fire was trying to read everything to, to, to get up and running.

Yeah, and it's such an obvious thing, but then afterwards it felt kind of magical, as if a few of those moments where I kind of added something and it just sort of, I think, transformed at least the way I use the RFD site. Full text search is one of them getting kind of discussion in line on the RFD site. Okay.

There's been a few versions of it. And I think like I kind of have a love-hate relationship with ASCII doc. I think it's amazing because it is so versatile and it is so painful because it's so versatile. You can create so much and I'm aware of a small subset of features. The RFD site is the place to check

like a renderer for ASCII doc, because you will see every version of, uh, of, of any way which you can use. That's good. It has been used on the RFD site and that will get kind of an issue now and again. And I'm just baffled. Cause I'm like, I didn't even know this was possible.

You should see the stuff people are doing. But the thing is, it's... It's really rewarding doing this stuff, but there's a balance, right? I don't want to spend all of my time working on like an ASCII doc renderer and kind of the styling for this thing if it's just kind of used in one place. And I think one way in which we have worked around that is we've embraced ASCII doc.