I cancelled my Replit subscription

Original Article ↗ Hacker News Discussion ↗

Replit’s recent pricing and product changes are prompting users to rethink paying for a cloud-based development environment, especially as cheaper plans disappear and AI coding features are bundled into more expensive tiers. Commenters weigh the convenience of one-click, browser-based setups for learning, interviews, and quick experiments against concerns about lock-in, surveillance, weak support for niche languages like Lisp, and the erosion of local, general-purpose computing skills. Many argue that while tools like Replit lower barriers for beginners, long-term sustainability, ethics, and control over one’s tooling and data remain unresolved trade-offs.

Use cases and appeal of Replit / cloud IDEs

  • One‑click, opinionated environments remove setup friction, especially for multi‑language, multi‑project work or when you lack the right hardware/OS.
  • Popular for quick prototyping, code interviews, pair programming, demos, and “code in production” experiments.
  • Some users love piping code from chatGPT straight into a running cloud app and deploying without touching local setups.

Local vs cloud development

  • Several commenters say local dev (with Docker, dev containers, VMs) is fast to spin up and more transparent.
  • VS Code Dev Containers and GitHub Codespaces are cited as similar or superior for serious work.
  • Automatic cross‑device syncing is mentioned as a remaining pain point for local setups.

Education and beginners

  • Replit is praised for letting novices experience “write code, see magic” quickly, reducing early frustration.
  • Others report students who started on Replit later struggle with gcc, Makefiles, debuggers, and basic CLI skills.
  • Some argue schools should pair hosted tools with a “missing semester”‑style course on tooling and OS basics.

Privacy, control, and “dystopian” worries

  • Strong concern that moving programming into proprietary cloud IDEs erodes personal computing, data ownership, and transparency.
  • Fears include surveillance, AI‑training on user code, lock‑in, rug‑pull risk, and future restrictions on what software can be built.
  • Similar worries are extended to Codespaces, vscode.dev, and Copilot as a slow “boiling frog” shift to managed platforms.

Pricing, AI bundling, and business model

  • The price jump from cheaper “Hacker” tiers to a $20/month “Core” plan is widely seen as steep, especially for hobbyists.
  • Many dislike paying more while losing features they care about and gaining AI features they don’t want.
  • Some defend price increases as necessary for sustainability; others view it as VC‑subsidized bait‑and‑switch or simple profit maximization.
  • A few wish for “dumb” plans without AI at lower cost.

Language support and Lisp / FP

  • Multiple commenters note the irony of weak Lisp support in a product named after REPLs.
  • The OP’s shift back to Lisp and weaker Lisp tooling on Replit is cited as a reason to leave.
  • A long subthread debates functional‑programming support in Python vs JavaScript, touching on list comprehensions, map/filter/reduce, lambdas, composition, pattern matching, and tail‑call optimization; consensus is mixed and largely subjective.

Alternatives and DIY solutions

  • Some replace Replit with a VPS plus Emacs/IDE for remote dev, or with self‑hosted “Replit‑like” setups using Docker, Nix, or immutable desktops.
  • Replit’s removal of simple REPLs and move toward a heavier in‑browser IDE is lamented by some early users.

Overall sentiment

  • Replit is praised as an excellent teaching and prototyping tool but increasingly criticized for pricing, AI focus, weaker niche language support, and broader concerns about cloud‑only development.