Show HN: Orange Juice – Small UX improvements that make HN easier to read

Original Article ↗ Hacker News Discussion ↗

Comparison with existing HN tools

  • Many compare Orange Juice to Refined Hacker News and other extensions/themes.
  • Orange Juice is presented as a clean rewrite inspired by Refined HN: updated for current HN DOM, with different architecture, more control over the page, more edge cases handled, and faster performance.
  • Some still use Refined HN forks and note feature parity but also bugs there; several users report switching to Orange Juice and preferring it.
  • Other tools mentioned: alternative themes via Stylus, comment UX extensions, “similar posts” extensions, and various HN frontends.

Desired features and UX changes

  • Popular or requested features:
    • Inline replies (reply box opens in place).
    • Unread/new comment highlighting.
    • Dark mode and easy light/dark toggle.
    • OP markers in comment threads.
    • Larger tap targets / better mobile usability.
    • Easier collapsing of threads (bars or moving [-]).
    • Keyboard navigation and focus highlighting.
    • Options to hide read stories and auto-collapse deep threads.
  • Some users dislike opinions baked in as defaults (all links opening in new tabs, focus box, dark-mode default) and ask for toggles; preferences are rapidly added.

Implementation & AI usage

  • The extension is heavily AI-assisted: AI wrote much of the code and “hundreds” of tests; CI/CD publishes automatically to stores.
  • Some praise the transparency and say AI plus human oversight feels trustworthy.
  • Others criticize the project as overengineered “AI slop,” focusing on:
    • ~2MB of JS for relatively small feature set (with mermaid as a known chunk).
    • Use of AI-generated browser logos instead of official assets.
    • Perceived unnecessary abstraction and complexity.

HN core philosophy vs extensions

  • Several commenters want HN itself to remain minimalist and stable, preferring enhancements to live in extensions or custom CSS.
  • Others argue that some features (dark mode, unread comment indicators, better typography) should be native by now.
  • A YC/HN maintainer clarifies that:
    • HN has full-time engineering support; the UI’s conservatism is intentional, not neglect.
    • The priority is content and discussions, with minimal UI changes, though future evolution is being explored.
  • There is disagreement over whether today’s “minimalism” should account for modern screens and accessibility (e.g., font size).

Platform and integration notes

  • Currently focused on Chrome/Firefox; Safari/iOS support is requested, with some uncertainty about the build/CI steps.
  • Some users prefer userstyles/userscripts (Stylus, *monkey scripts) to reduce extension attack surface.
  • A few report visual glitches (flash of unstyled HN before enhancements, Firefox page reload quirks).