A website for debloated open source alternatives

Original Article ↗ Hacker News Discussion ↗

A new site, debloat.dev, curates lightweight open‑source alternatives to popular “bloated” software, drawing praise for its fast, retro, JavaScript‑free design but also criticism for relying on Google/GitHub logins and having certificate/access issues. Commenters debate what actually counts as “bloat,” questioning entries like Tailscale and Nextcloud and noting how some domains, such as media centers, have consolidated around a few heavyweight projects despite tools like ffmpeg lowering technical barriers. Broader themes emerge around the tension between simplicity and feature creep, the impact of venture funding on open source, and how to assess software quality in an era of AI‑assisted code.

Media centers and complexity

  • TV/Media category shows many XBMC/Kodi entries; some see this as consolidation and loss of variety versus 10–15 years ago.
  • Explanations offered:
    • Media center support is technically and UX-wise complex (formats, transcoding, acceleration, metadata).
    • ffmpeg is powerful but vast; deep understanding can be a specialization.
    • Transcoding itself is described by several as “the easy part”; building polished UX, catalogs, and dealing with users is the real burden.
  • Disagreement on audio vs video difficulty:
    • One side: video servers are much more complex (transcoding, subtitles, hardware accel, metadata scraping).
    • Other side: audio and video share the same fundamental problems (indexing, multiple formats, front-end widgets).

Ebooks and other self-hosted tools

  • Calibre long dominated ebook management; newer tools like Grimmory and Shelfmark are cited as better-UX successors or complements.

What counts as “bloat”

  • Some treat the site as “open-source alternatives” rather than rigorously “debloated.”
  • Debate around Tailscale: seen as useful but suffering feature creep; tension between investor-driven growth and minimalism.
  • Claim that capitalism and FOSS are incompatible is countered by pointing to their current coexistence.

Code style and consistency debates

  • Suckless-style strict rules (e.g., comment syntax) are mocked as bikeshedding and low-value.
  • Counterview: any single style is fine as long as it’s consistent; consistency aids comprehension.
  • Another view rejects “consistency” as a meaningful metric, arguing focus should be on tests and algorithms; others push back that consistent style genuinely improves readability.

Authentication and privacy

  • Google/GitHub-only login is criticized; some want simple email or site-local accounts.
  • Irony noted: a “debloat” site relying on big-tech OAuth.

Site reliability, UX, and implementation

  • Many report TLS/SSL errors, AV blocks, or corporate firewall blocks; some suspect load/capacity issues, others mention certificate problems.
  • Others see valid Let's Encrypt certs; overall cause is unclear.
  • The site is praised for:
    • 1990s/early-2000s “eBay-like” retro design.
    • No JavaScript, no cookies, minimal CSS.
    • Fast loading and compatibility with text-only browsers; all pages discoverable via sitemap.
  • Some suspect “vibe-coded” / AI-like HTML but this is not established.

Alternative directories and specific tool mentions

  • alternativeto.net is mentioned as a long-standing resource, but criticized as bloated and less usable after redesign.
  • Alternatives suggested: SaaSHub, openalternative.co, tinyapps.org.
  • Specific tools praised:
    • Nextcloud is called powerful but not “debloated”; no clear single lighter replacement.
    • Immich cited as a strong Google Photos replacement.
    • G-Helper for Asus laptops.
    • Kanboard as a lightweight Trello alternative.
    • Various ebook and media tools (Calibre, Grimmory, Shelfmark, Jellyfin, VLC, gstreamer).

AI-generated code and “slop”

  • Some want markers for “AI-generated slop.”
  • Others ask how “slop” is defined and question whether well-tested AI code is inherently worse than mediocre human code.
  • Concern raised that requests for rigor around AI are often shut down; underlying issue framed as “how are you filtering for quality?”

Performance, APIs, and bloat control in projects

  • One commenter argues maintainers should treat performance as a first-class feature and refuse features that expand API surface at throughput’s expense.
  • Suggestion to keep a minimal core module and “strangle” additional features into separate wrappers, with tests guarding invariants.

“Debloating” beyond software (cars)

  • Desire expressed for a “debloated” electric car.
  • Some examples given of relatively conventional EVs with simpler interfaces and physical controls.
  • Concerns about always-connected cars, built-in SIMs, GPS tracking, and integration with big-tech ecosystems like Android Auto.
  • Debate over whether Android Auto is inherently privacy-invasive; some claim it can be used offline with minimal data sharing, but legislative gaps and data collection concerns remain.