gokulsiva

4 ms·

1.
by gokulsiva 9mo ago
This looks very compelling from a DX perspective — especially the “local JSON that just syncs” mental model. Just curious - What conflict resolution model are you using (CRDTs / OT / something else), and how deterministic is it un
2.
by gokulsiva 9mo ago
you mean node ?
3.
by gokulsiva 9mo ago
Yeah, that matches my experience too — Chrome gets you ~80% there, but the missing pagination primitives push you into extra layers like paged.js. I’ve also hit issues with tables and page breaks. Curious if TOC was the main blocker for you
4.
by gokulsiva 9mo ago
That makes sense. Have you run into any pain points once documents got large or more structured (tables, headers/footers, multi-page), or has HTML held up fine for you so far?
5.
Ask HN: What made you move back to HTML-to-PDF in production?
6 points by gokulsiva 9mo ago|7 comments
6.
Show HN: Pdfn – React-based PDF generation with Chromium(pdfn.dev)
3 points by gokulsiva 9mo ago|0 comments
7.
by gokulsiva 1y ago
Would love feedback on the API design and what file operations you need for your AI apps.
8.
Show HN: OpenFiles – Persistent cloud files for AI agents(openfiles.ai)
1 points by gokulsiva 1y ago|1 comments
9.
by gokulsiva 1y ago
Hi HN! I'm excited to share ODocs with you today. I built it to solve a frustrating problem I kept encountering with AI coding assistants - they generate outdated or incompatible code because they have no idea about which framework ver
10.
Show HN: ODocs – Make AI coding assistants generate compatible code on first try(odocs.dev)
2 points by gokulsiva 1y ago|1 comments