Uchū – Color palette for internet lovers

Original Article ↗ Hacker News Discussion ↗

Use Cases and Examples

  • Many commenters liked the palette but wanted to see it applied to a “real” UI: dashboards, app interfaces, or text-heavy layouts, with clear mapping of colors to roles (backgrounds, borders, accents, etc.).
  • The author shared existing and upcoming sites plus a social network prototype using the palette, but several people still felt there wasn’t enough immediate guidance on how to recreate the look.
  • Some users immediately applied the palette to personal apps (e.g., a recipe web app) and plan to build editor/Emacs themes or app themes with it.

Implementation, Tooling, and Browser Support

  • Palette is defined in OKLCH with CSS variables, including “raw” variants to support opacity control like oklch(var(--color-raw) / 40%).
  • It uses modern CSS features (OKLCH colors, nesting), which broke the site for some users on older Firefox/Chromium and iOS Safari, who saw only black text on white.
  • Several tools and alternatives were mentioned: grayscale.design, Tailwind’s and Open Color palettes, Huetone, inclusivecolors.com, oklch.com, OKLCH visualizers, and other curated schemes like Flexoki.
  • People asked about integration with Tailwind, Chrome themes, and editors; suggested preconverting to RGBA/hex for broader compatibility.

Accessibility, Contrast, and Dark Mode

  • One thread questioned low contrast for long-form reading. The author said some swatch text is decorative and wouldn’t be used for paragraphs.
  • This triggered a large debate:
    • One side argued current accessibility pushes (very high contrast, large fonts, forced themes) can make UIs “ugly,” tiring, and should instead be personalized via OS/browser settings or extensions.
    • Others countered that contrast and color choices significantly affect many users (older users, people with low vision or color-blindness, light sensitivity), and good defaults still matter.
    • Several stressed that needs conflict (some require high contrast, others low brightness) so designs need “levers,” not one fixed setting.
  • Color-blind users reported some hues (especially middle columns) as nearly indistinguishable; a simplified palette variant was offered.
  • Tools showed the palette is not perceptually uniform; some see that as a drawback for systematic design, others as a stylistic choice.
  • The site does not honor dark-mode preferences and can’t be easily darkened by extensions, which a few found jarring or hostile at night.

Naming and Cultural Discussion (“Uchū”)

  • Multiple comments questioned the trend of naming tech projects after single Japanese words without deeper connection.
  • There was extended back-and-forth on whether “uchū” is better translated as “space,” “cosmos,” or “universe,” and how closely it really maps to “universal.”
  • Some argued using words from a language you don’t speak is superficial or “aesthetic appropriation”; others replied that product naming is inherently free-form, loanwords are normal, and Japanophilia in tech makes such names popular and recognizable.

Site UX and Miscellaneous Feedback

  • The landing section (full-height, “SCROLL” indicator) divided opinion: some saw it as a fun nudge, others as evidence of poor affordance (like a loading screen needing “click here”).
  • Suggestions included leaving content visibly cut off to imply scroll, aligning with Material/Metro guidelines, and reducing the hero height; the site was later adjusted.
  • Complaints surfaced about back-button behavior and an animated SVG favicon that caused high CPU usage in a browser’s bookmarks bar.
  • Overall sentiment on HN ranged from enthusiastic (“beautiful,” “exactly what I needed”) to dismissive (“just boxes of colors,” “not needed”), with meta-discussion on why such a simple palette page can become so popular.