From where I left

Original Article ↗ Hacker News Discussion ↗

Return to Redis and New Vector Features

  • Many welcome the original creator’s return to Redis and are excited about the new “vector sets” / vector search work.
  • The proposed API is praised for simplicity and “learn in 120 seconds” design; some see it as a badly needed alternative to today’s complex vector DBs.
  • A few disagree with the “vector set” design direction but appreciate that multiple forks allow experimentation toward “the better Redis.”

Redis vs. Valkey and the License Schism

  • A major thread is whether to use Redis (now under RSAL/SSPL-style licenses) or Valkey (the open-source fork).
  • Some treat Valkey as the “main line” continuation of the original BSD Redis, with Redis now a proprietary fork.
  • Others argue the “real” Redis is defined by design and core team, not license; they’ll stick with the brand and its engineers.

Licensing, SSPL, and Trust

  • Many are upset by the license change, calling it a “rug pull” that breaks an implicit social contract with contributors and users who expected BSD forever.
  • Others counter that BSD/mit explicitly allows relicensing, and that contributors unhappy with this should have chosen copyleft and avoided CLAs.
  • SSPL is seen by some as “almost AGPL + SaaS restriction”; by others as dangerously broad, hard to comply with, and legally ambiguous (e.g., requiring all “service source code” under SSPL, possibly conflicting with Linux/glibc, etc.).
  • There’s concern about future changes and “booby-trap” licenses vs. the predictability of OSI-approved ones.

Cloud Providers and OSS Economics

  • Strong disagreement on who is “the bad guy”:
    • One side: cloud providers parasitize OSS, commoditize it, and capture most revenue; restrictive licenses are a justified defense.
    • Other side: these projects built their popularity on permissive licenses and community work; changing rules after success harms trust and the broader OSS ecosystem.
  • Valkey’s backing by major clouds and the Linux Foundation is seen both as:
    • A positive, sustainable way to keep an open fork healthy.
    • And as big tech using “community” branding to maintain their margins.

AI Tools (Claude vs. ChatGPT) and Developer Workflow

  • Multiple commenters affirm Claude’s usefulness for coding, design, and even fiction editing, often preferring its style and lower “prompt wrangling” overhead to ChatGPT.
  • Others report better results with ChatGPT for certain reasoning or math-heavy tasks.
  • Several describe AI tools as huge productivity multipliers and as emotional “support” for solo devs.

Meta: Community, Contribution, and Future

  • Some maintainers/contributors say they were not personally bothered by the relicensing and still see value in both Redis and Valkey.
  • Others say the incident makes them more cautious about contributing to or depending on projects with CLAs or corporate control.
  • Many express continued admiration for the technical work but plan to default to Valkey for future deployments.