gokulsiva's comments

gokulsiva | 1 month ago | on: Jazz – The Database That Syncs

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 under concurrent offline edits?

gokulsiva | 1 month ago | on: Ask HN: What made you move back to HTML-to-PDF in production?

you mean node ?

gokulsiva | 1 month ago | on: Ask HN: What made you move back to HTML-to-PDF in production?

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, or if there were other cases where Chrome alone didn’t hold up.

gokulsiva | 1 month ago | on: Ask HN: What made you move back to HTML-to-PDF in production?

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?

gokulsiva | 6 months ago | on: Show HN: OpenFiles – Persistent cloud files for AI agents

Would love feedback on the API design and what file operations you need for your AI apps.

gokulsiva | 11 months ago | on: Show HN: ODocs – Make AI coding assistants generate compatible code on first try

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 versions your project is using or new versions and patches released.

How it works:

1. ODocs uses a CLI tool that provides latest version details of popular packages and also scans your project files (like package.json) to detect which frameworks and versions you're using. 2. It fetches the correct version-specific documentation from our open registry. 3. It runs a local server that AI coding assistants can connect to via API or MCP (Model Context Protocol). 4. When you ask for help, your AI assistant uses the right documentation for your exact versions.

Technical stack:

- Node.js CLI tool for framework detection - Hono-based API server for documentation serving - Local caching system to minimize network requests - Open documentation registry (similar to Docker Hub model)

Current status: The initial prototype works with Hono 4.7.5 (a lightweight web framework). This targeted implementation proves the concept works, but we're just getting started.

What's next: We're focusing next on adding support for:

React ecosystem (React, Next.js) TailwindCSS Common Python frameworks

This is fully open-source, and we'd love contributions to expand framework support or improve the project!

Which frameworks would you most like to see supported next? Your feedback will help guide our priorities.