DevDocs

Original Article ↗ Hacker News Discussion ↗

Developers highlight DevDocs.io as a fast, consolidated, and offline-capable documentation browser that significantly boosts productivity, especially on flaky connections or long flights. They compare it to tools like Dash and Zeal, discuss editor integrations and CLI frontends, and note gaps such as missing C# docs due to licensing concerns. The conversation broadens into the importance of easily accessible offline documentation for open source software, trade-offs in documentation formats and generators, and how emerging tools like LLMs might complement or eventually reshape how technical knowledge is consumed.

Overall sentiment & use cases

  • Many commenters say they’ve relied on DevDocs for years and keep it pinned or integrated into their workflow.
  • Offline access is highlighted as critical on planes, with flaky Wi‑Fi, and in distraction‑free setups; several report being more productive offline with DevDocs plus local tools/LLMs.
  • Some developers say they practically don’t code without internet (Google, MDN, ChatGPT), so offline docs feel less essential to them.

Comparisons & alternatives

  • Frequently compared to Dash (macOS) and Zeal (open source, multi‑platform); DevDocs is seen as a web‑first, open alternative.
  • Users value Dash’s ability to pull from ReadTheDocs and user‑contributed docsets; DevDocs is noted as lacking some of that.
  • Other tools mentioned: dedoc (CLI for DevDocs), devdocs-desktop, Vim/Neovim/Emacs plugins, Zeal user-contributed docsets, local browsers like CHM, GNU info, man pages.

Offline documentation formats & standards

  • Discussion about packaging formats for offline docs: ZIPped static sites, Markdown, AsciiDoc, Dash “docsets”, GNU info, ePub, CHM.
  • Tradeoffs noted: images vs size, per-version docs, JS-heavy sites being harder to mirror, and browsers dropping support for some formats.
  • Some want a standardized, RSS‑like way to announce “offline-friendly” docs; nothing widely adopted was identified.

DevDocs features, gaps, and technical issues

  • Appreciated for speed, unified search across many APIs/languages, and offline mode.
  • Requests for more ecosystems: C#, Playwright, mobile/OS SDKs, Common Lisp, Java confusion (present as “OpenJDK”).
  • C#/.NET docs are constrained by perceived licensing issues, though others point to CC‑licensed Microsoft docs and GitHub repos.
  • Complaints: Firefox and some browsers evict offline storage; local storage resets can wipe selected doc sets.
  • Maintainer explains docs are scraped from HTML; JS-heavy and randomly‑named CSS complicate scraping and cleanup; outdated-docs reports are generated monthly.

Philosophical debate: offline docs, openness, and LLMs

  • One long subthread argues that easy offline access to full documentation should be considered as fundamental as source availability in FOSS.
  • Others respond that:
    • The bigger issue is doc quality, not just offline access.
    • Many users will be better served by intuitive UIs than by docs.
    • LLMs increasingly answer questions faster than traditional docs, potentially reducing the long‑term importance of tools like DevDocs.