Tag

Rails

2 stories

A Ruby developer archived every gem he wrote, citing Matz's pivot to the AI age (po-ru.com)

Paul Battley, a London developer, archived all his Ruby gems and wrote that he no longer wants to feed a commons that big companies strip-mine for machines. He points at Ruby's own core team, which he says now builds the language largely with LLM agents.

In the thread, the founder of an email company described a friend on an 80K-star project who is disillusioned too: the robots work, but the joy of collaborating is gone.

Not just a headline — the discussion unpacked

The top HN threads: facts from the discussions, both sides, insider voices. Email, Telegram, or RSS.

One Ruby gem, 12 AI providers, 800 models, and a maintainer bottleneck (rubyllm.com)

The pitch: 12+ providers and 800+ models behind a single API with three dependencies, chat, vision, embeddings, tools, and a Rails acts_as_chat hook.

Shipping shops vouch for it, but the leaky edges surface fast: prompt caching that breaks per-provider, and a maintainer whom a Rubygems.org founder says merges vibe-coded PRs while ignoring real ones.