November 28, 2025
From hype to type
Generating 3D Meshes from Text
No, it’s not AI—just chunky 3D letters you can play with
TLDR: A dev built a pipeline to turn written text into solid 3D letters, not AI-generated models. The comments split between praising practical, non-AI engineering and grumbling about expectation bait, with extra snark over using an AI assistant to scaffold the tiny Bun server.
The crowd clicked expecting an AI fever dream that turns sentences into full-blown 3D objects… and instead found a crafty, hands-on pipeline that turns actual text into actual 3D letters you can extrude and render. One top comment nailed the mood: this isn’t Microsoft’s Trellis magic—it’s good old “make the letters thick.” Cue gasps, relief, and a few “finally, something that doesn’t hallucinate” memes.
The builder uses svg-text-to-path to outline letters, a tiny Bun server to keep it light (and hide a Google Fonts key), and font shaping via fontkit. Non-technical translation: it traces the shape of your text, then turns those outlines into solid 3D like cookie cutters with depth. Some cheered the practicality—“boring but useful” engineering is back—while others accused the title of AI-bait. The dev admitting they used an LLM to scaffold the backend sparked fresh drama: half the thread said “perfect use-case,” the other half clutched pearls at “AI wrote my server.” Font gossip? A few obscure fonts failed to load, inspiring jokes like “Papyrus dodged a bullet” and “Can it do Comic Sans, but… thicc?” In short: less hype, more heft, and a whole lot of spicy expectations management.
Key Points
- •The pipeline converts text into SVG paths using the svg-text-to-path JavaScript library.
- •Google Fonts is used as the font provider, requiring a free API key to access a wide range of fonts.
- •The default fontkit backend performs the text-to-path conversion, offering advanced font features.
- •A minimal Bun-based backend (using Bun.serve) exposes an HTTP/JSON endpoint to securely handle font loading and caching.
- •The service outputs a string of SVG path commands; further steps (e.g., via lyon) follow after path generation, not detailed in the excerpt.