Gloomberb

Original Article ↗ Hacker News Discussion ↗

An open‑source, Bloomberg‑inspired terminal called Gloomberb is drawing interest for its sleek, tiling interface but skepticism over its reliance on free data sources like Yahoo and SEC filings, which limit historical depth and real‑time quality. Commenters stress that Bloomberg’s true moat is not its UI but its costly, curated data feeds and its gated chat network that underpins much of institutional bond trading. The project also triggers broader concerns about “AI‑generated slop,” insecure `curl | bash` install scripts, and whether vibe‑driven tools built in JavaScript or TypeScript are appropriate for workflows involving financial data and trust.

Data sources & capabilities

  • Commenters identify Yahoo Finance and SEC/EDGAR filings as main data sources, via the linked GitHub repo.
  • Several note this is weak for deep historical data; serious history usually requires expensive data subscriptions.
  • Some suggest the app is useful for presentation and quick access to public data, but not remotely comparable to professional feeds.

Website, installation & stack

  • Multiple users report broken or inconsistent UI (logo rendering, download buttons, docs 404, empty blog), others say it works fine on their setups.
  • Confusion over download links (macOS vs Windows) and missing documentation makes some question project polish.
  • The curl | bash installer and JavaScript/TypeScript stack trigger pushback: concerns about supply-chain risk, runtime bloat, and clashing with existing JS tooling.
  • Others counter that it’s open source, binaries are available, and convenience often drives these choices.

Bloomberg comparisons & data economics

  • Many emphasize people pay Bloomberg for data breadth, quality, and integrations, not just a terminal UI.
  • There is skepticism that any cheap/open alternative can replicate those data relationships; quality financial data and leased lines are described as inherently expensive.
  • Some argue financial information “should be free,” others respond that its exclusivity is what creates value.
  • The project name invites Bloomberg comparison; some see it as playful, others think it unintentionally positions the tool as a “Bloomberg clone.”

Messaging, network effects & who actually needs Bloomberg

  • Several posts stress Bloomberg chat as a major moat: bond and OTC trades are often negotiated directly in Bloomberg DMs.
  • The subscription itself acts as a gatekeeping signal that participants are serious and solvent, like a “country club” for finance.
  • Others argue data is at least as important as chat, and that alternatives exist for some asset classes and use cases.

Open source expectations & AI/“slop” concerns

  • Debate over whether critics of bugs/UX in open source should submit fixes vs. simply offering feedback.
  • Some users now assume new “vibe-coded” TUIs are partially or heavily LLM-generated “slop” and are wary of trusting them, especially with anything sensitive.
  • Others note nearly everyone uses LLMs to some extent and argue the real question is whether the project is crafted with care, not whether AI was involved.

Perceived usefulness & target audience

  • A number of commenters find the aesthetic and tiled interface appealing and potentially a good replacement for multiple browser tabs.
  • Willingness to pay for the pro/cloud subscription is mixed; many say they wouldn’t pay for what browsers + existing tools already provide.
  • Some see Bloomberg-style terminals and even finance UIs generally as overkill or “horoscopes” for retail traders, offering little long-term edge.