Still haven’t used the library! 🤷♂️ Just wanted to see if I could go from idea to publish on an open source project on a whim.
The whole process took about 15 minutes.
Wonder if this is a similar feeling as going across an ocean by airplane when airplanes were new.
Rather than copy and paste the files, I asked o1 to write a script that would `cat` out all of the files in one go for me, and it did.
I ran its script; fixed one compiler error. Unit tests and sanity check passed.
So I documented & published it: https://t.co/67Bqime4DK https://t.co/Fl4BbPB9y4
Then I asked o1 to package its solution as a crate, labeling file names with their contents, along with unit tests, that I could publish without further intervention.
My prompt specified management of `Arc` and ` Weak` for nodes vs. edges of the graph, to handle the memory leak hazard of circular references , while leveraging `Arc`s advantages as a concurrency-friendly smart pointer.
This approach results in a very simple implementation; this is a famously unergonomic problem in Rust.
@rauchg Exactly the opposite — the lowest-entropy solution will win as LLMs bring switching costs to zero.
This is bigger than frameworks: LLMs will bring us to a post-HTML world.
HTML/CSS are a poor substrate for UIs: complicated, legacy, perf, visuospatially mangled
What comes next?
Nvidia breaking a $3T market cap is inspirational. Designing chips for Nvidia could have been my career path after college! But that wasn't my passion.
Nonetheless, I will celebrate that I just used my higher education to repair my dead refrigerator for $8 in parts.
Check out @warfajibril building our website in Pax Create. Visual building + natural language + code, all affecting the same substrate. This is the future of building software.
Today for the first time, I talk about what I've been building for the last 18 months: Pax. I'm thrilled to partner up with @warfajibril to make software creation more accessible, more creative, and more collaborative! Read more: https://t.co/0BVwwcP7au