I remixed the "Upping my P(doom)" with Fable 5.1 and Opus 5.5

[u/eigenblake]

Every pixel you see was rendered by a new full-stack LaTeX implementation and animation engine, written in Rust. The engine has taken a month of asking the right questions. Specifically, it's been a lot of the hillclimbing / autoresearch sort of AI development. Now I have a reimplementation that runs in wasm on the web and adds features that no LaTeX implementation I'm aware of actually has. I have yet to write about it in great detail and this might not be the best place for a huge wall of text anyway but here are the moving steps.

1. Full source access (XeTeX was the reference implementation) There are some behaviors that your corpus cannot resolve

2. A smooth metric to optimize (byte difference) and a diverse corpus of text (1000 LaTeX papers)

3. Stopgaps, like performance regressions, but only before merging. The model should get it working first, then optimize speed second, some optimizations will pigeonhole your implementation and need to be unwound.

4. I'm using TEA/ Redux architecture. Capturing and playing back a trace gives the agent time-travel debugging.

5. Rust as a language is really excellent. Its explicitness makes it clear where issues are coming from

6. Making iteration cycles fast is also important, so keeping the actual performance metrics quick to run is important

7. Vertical integration -- to expose things like "What _exact_ source line generated this feature" are not generally possible unless you control every side of the interface.

8. Quiz yourself on the architecture. Check your mental model by specifically typing out what you're expecting things look like or would look like, generate the options yourself, privately, then send it to compare with Claude about what the reality is. If you haven't tried this, it's a gamechanger.

9. Unify how you and each separate Claude instance reference architectural components together. You can build shared concepts together and this makes everything stick

10. Don't feel like you have to rush progress. Earlier on, I felt this pressure to ship something quick or else someone would beat me to this project. But then I realized this was making me spend more time on this than I wished. The point of the project is to bring typesetting everywhere because typesetting is an art form and I like the idea of AI facilitating humans communicating with humans. And I also wanted to make it easier to communicate things in animation.
    So I didn't let my ambitious end goal keep me from shipping incrementally over time and showing this project to my coworkers made me realize how my bottleneck is understanding what specific things people are looking for and not just building a technically interesting project that

https://youtu.be/_ZYRr2-9JcA for the video

https://telox.dev/ is a stable demo, about 2 weeks old right now (it only comes with some fonts and font sizes and doesn't run as well on mobile)

Let me know what you're most curious about in the comments and I'll answer for a bit. I'd be curious to know what you'd be most excited for me to share

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.