701 karma · joined March 5, 2007
YC Badge: 0x9f3c73b54ee1eaff7e5f0575d70ca412f6225ef5
* I wrote a similar article around making "blobs" a while back: https://www.hailpixel.com/articles/generative-art-simple-mat...
Ya'll might want to switch from V0 to claude code.
But I agree with you, a great use case for a Next.js-esque static site.
Which, isn't even a word, but I enjoy the internet doing classic internet things.
Edit: It is now `no`. Amazing.
Best of luck with this version!
Anyway, neat crane idea.
Always wondering if you could just stick it in a vacuum pump...
On a more meta note, how you approach writing your book is probably more impactful than your toolchain. If you're working on a book that educates (rather than, say, entertains), I'd like to share the writing framework that my longtime collaborator, robfitz, describes in Write Useful Books (https://www.usefulbooks.com/). Basically, treat your book like a product, find your audience, and test your subject matter with them as your craft your prose.
* Disclaimer: Rob and I run Useful Books, a community and toolset for non-fiction authors.
1. It's works extremely well with the current component-focused UI frameworks (react, svelte, etc). Subsequently, the verboseness that is often a complaint isn't an issue at all, but a feature.
2. Does everything out of the box, and very easy to customize.
3. And, most importantly, it allows for easy art direction. Does one button need to be a slightly different size or color for this one specific element? Chuck an extra modular class on it. No need to build a complex cascasding or edge cases. (Shout out to `tailwind-merge`)
Point 3 for me speeds up production work immensely. Also, not being in JS has shrunk bundle sizes by a small amount, which is always welcome in this era.
[Boundless](https://boundlesshq.com/) is a startup that is tackling this exact problem through automating the entire "employe(e/r) of record" process.
Who's the audience here?
Fun though.