rip-lang 2.9.0 → 2.9.2

package/docs/WHY-NOT-COFFEESCRIPT.md

@@ -1,186 +0,0 @@
-<p><img src="rip.svg" alt="Rip Logo" width="100"></p>
-
-# Why Not CoffeeScript: The Case Against Revival
-
-## Executive Summary
-
-CoffeeScript 2 already achieved the goal of modern JavaScript output in 2017. Any effort toward further CoffeeScript development in 2026 represents a misallocation of resources toward a language that has been definitively superseded by the JavaScript ecosystem's evolution. This document presents the compelling case for why CoffeeScript should remain a respected historical artifact rather than receive continued development.
-
-**TL;DR:** The ecosystem has moved on. The tooling has rotted. The community has dispersed. TypeScript won the type safety war. Modern JavaScript absorbed the best ideas. What's left isn't worth the cost.
-
-## The Fundamental Misconception
-
-Many assume CoffeeScript needs updating to output ES6+. **This is false.** CoffeeScript 2 (released 2017) already generates:
-- ES6 classes with `extends` and `super`
-- Arrow functions with lexical `this`
-- Destructuring assignments
-- Template literals
-- `for...of` loops
-- ES6 modules (`import`/`export`)
-- Spread operators
-- Computed property names
-
-The output is already modern. The problem isn't technical—it's existential.
-
-## 1. Ecosystem Abandonment: The Network Effect in Reverse
-
-### The Developer Desert
-- **Hiring Crisis**: Try posting a "CoffeeScript Developer" position in 2026. You'll get tumbleweeds or developers who haven't touched it since 2015.
-- **Knowledge Decay**: Senior developers who knew CoffeeScript have moved on. Junior developers have never heard of it.
-- **AI Blindness**: GitHub Copilot, ChatGPT, and other AI assistants are trained on modern codebases. Their CoffeeScript suggestions are often outdated or incorrect.
-- **Dead Community**: The CoffeeScript forum has ~5 posts per month. The TypeScript forum has ~500. The network effect that once benefited CoffeeScript now strangles it.
-
-### Library Lockout
-- **TypeScript Hegemony**: Every major library ships with `.d.ts` files. Using them from CoffeeScript means abandoning type safety entirely.
-- **No Native Integrations**: Modern frameworks (Next.js, Nuxt, SvelteKit) assume TypeScript or JavaScript. CoffeeScript requires custom configuration that often breaks with updates.
-- **Security Vulnerabilities**: When was the last time CoffeeScript's dependencies were audited? The maintenance burden falls on a tiny, overwhelmed community.
-
-## 2. The Type Safety Revolution Left CoffeeScript Behind
-
-### TypeScript Won by Solving Real Problems
-- **Refactoring at Scale**: Rename a method in TypeScript, and your IDE updates every call site. In CoffeeScript, you grep and pray.
-- **API Contracts**: TypeScript interfaces document and enforce API contracts. CoffeeScript relies on... documentation? Comments? Hope?
-- **Compile-Time Catches**: TypeScript catches errors before runtime. CoffeeScript catches them... in production.
-- **IntelliSense**: Modern developers expect autocomplete that actually works. CoffeeScript's IDE support is "here's a list of every word in your file."
-
-### The Cost of Being Typeless in 2026
-- **Integration Nightmare**: Every third-party library requires manual type annotations or living without IDE support
-- **Team Scaling Breaks**: CoffeeScript works for 1-2 developers who hold the entire codebase in their heads. At 10+ developers, the lack of types becomes a coordination disaster.
-- **No Migration Path**: You can gradually adopt TypeScript in a JavaScript codebase. CoffeeScript requires a full rewrite.
-
-## 3. Tooling Degradation: Death by a Thousand Cuts
-
-### IDE Abandonment
-- **VS Code**: CoffeeScript extension last meaningful update: 2019. TypeScript: Updated weekly. The gap widens daily.
-- **WebStorm**: CoffeeScript support officially deprecated as of 2024. JetBrains gave up.
-- **Vim/Neovim**: CoffeeScript LSP? Might as well ask for a steam-powered smartphone.
-- **GitHub Copilot**: Trained on modern codebases. CoffeeScript suggestions are often wrong or outdated.
-- **Cursor/AI IDEs**: The future of development doesn't include CoffeeScript in their training data.
-
-### Build Tool Afterthought
-- **Vite**: Requires a third-party plugin that breaks every major update
-- **Webpack**: CoffeeScript loader is in maintenance mode
-- **Bun**: Can bundle TypeScript natively. CoffeeScript? "What's that?"
-- **Deno**: Built for TypeScript-first development. CoffeeScript is alien technology.
-
-### Developer Experience Regression
-- **No Prettier Support**: Your team will have formatting wars like it's 2010
-- **ESLint**: Limited rules, most plugins incompatible
-- **Source Maps**: They exist, but debugging through transpilation layers is always worse than native
-- **Hot Module Replacement**: Works... sometimes... if you hold your mouth right
-
-## 4. Modern JavaScript Didn't Just Catch Up—It Surpassed
-
-### JavaScript Absorbed CoffeeScript's Best Ideas
-- **Optional Chaining**: JS `?.` is everywhere now
-- **Nullish Coalescing**: JS `??` handles null/undefined elegantly
-- **Arrow Functions**: JS `=>` is more explicit about `this` binding
-- **Destructuring**: JS destructuring is more powerful and flexible
-- **Classes**: JS classes are native, optimized, and well-understood
-- **Template Literals**: JS backticks are standard
-
-### What's Left Is Not Enough
-- **Significant Whitespace**: Python developers like it. JavaScript developers see it as a footgun.
-- **Implicit Returns**: Causes more bugs than it prevents. Explicit is better than implicit.
-- **Everything is an Expression**: Clever, but creates debugging nightmares.
-- **Existential Operator**: JavaScript's `?.` and `??` cover 95% of use cases more clearly.
-
-## 5. The Performance and Security Argument
-
-### Runtime Overhead
-- **Extra Transpilation**: Every file goes through an additional compilation step
-- **Larger Bundles**: CoffeeScript's runtime helpers add weight
-- **Slower Development**: Live reload, HMR, all slower due to the compilation step
-- **Memory overhead**: Build tools keep both CS and JS versions in memory
-
-### Security Concerns
-- **Supply Chain Risk**: CoffeeScript itself is a dependency with minimal maintenance
-- **Outdated Dependencies**: The CS ecosystem doesn't get security updates quickly
-- **Audit Complexity**: Security tools are built for JS/TS, not CoffeeScript
-
-## 6. The Business Case Against CoffeeScript
-
-### Technical Debt Multiplication
-- **Training Costs**: Every new hire needs CoffeeScript training
-- **Maintenance Burden**: You maintain both the code AND the build pipeline
-- **Migration Inevitable**: Every CS codebase eventually migrates to JS/TS
-- **Opportunity Cost**: Time spent on CS tooling is time not spent on features
-
-### Project Risk Factors
-- **Bus Factor of One**: Often only one person really knows the CS codebase
-- **Vendor Lock-in**: Stuck with outdated tools that support CoffeeScript
-- **Recruitment Nightmare**: Developers actively avoid CoffeeScript positions
-- **Technical Isolation**: Can't easily adopt new tools, libraries, or practices
-
-## 7. The False Economy of Syntax Sugar
-
-### The "Conciseness" Trap
-CoffeeScript is more concise, but:
-- **Readability > Brevity**: Explicit code is easier to maintain
-- **Debugging Nightmare**: Less syntax means more implicit behavior to debug
-- **Onboarding Barrier**: New developers need to learn a whole new syntax
-- **Copy-Paste Broken**: Can't use code examples from Stack Overflow, documentation, or AI assistants
-
-### The Real Cost of "Beautiful" Code
-- **Cognitive Load**: Developers must mentally transpile CS to JS to understand behavior
-- **Error Messages**: Stack traces reference generated JS, not source CS
-- **Code Review**: Reviewers need CS expertise, limiting your reviewer pool
-
-## 8. The Innovation Dead End
-
-### Language Evolution Frozen
-- **No New Features**: When was the last significant CoffeeScript language feature?
-- **No Standards Process**: JavaScript has TC39. CoffeeScript has... GitHub issues?
-- **No Corporate Backing**: Microsoft backs TypeScript. Who backs CoffeeScript?
-
-### Missing Modern Features
-- **No Decorators**: The rest of the ecosystem is adopting them
-- **No Private Fields**: Modern JS has `#private`, CS has... conventions?
-- **No Pattern Matching**: TC39 is working on it for JS, CS will never get it
-- **No Type Parameters**: Generic programming is impossible
-
-## 9. The Maintainer Burden
-
-### The Human Cost
-- **Burnout**: The few CS maintainers are overwhelmed
-- **No Succession Plan**: When current maintainers leave, who takes over?
-- **Feature Requests**: The backlog grows while maintainer energy shrinks
-- **Breaking Changes**: Fear of breaking existing code prevents evolution
-
-### The Quality Spiral
-- **Bug Accumulation**: Bugs pile up faster than they're fixed
-- **Documentation Rot**: Outdated docs are worse than no docs
-- **Example Decay**: Sample code uses patterns from 2015
-
-## 10. The Strategic Dead End
-
-### No Path Forward
-- **No Migration Strategy**: You can't gradually move from CS to modern alternatives
-- **No Ecosystem Integration**: New tools don't consider CoffeeScript at all
-- **No Corporate Use Cases**: No major company is choosing CoffeeScript for new projects
-- **No Educational Value**: Bootcamps and universities don't teach it
-
-### The Opportunity Cost
-Every hour spent on CoffeeScript 3 could be spent on:
-- **Learning Rust/Go/Zig**: Languages with actual momentum
-- **Contributing to TypeScript**: Where improvements benefit millions
-- **Building Tools**: That solve real problems for modern developers
-- **Creating Libraries**: That the ecosystem actually needs
-
-## The Verdict: Let It Rest
-
-CoffeeScript served its purpose. It showed JavaScript could be better and influenced ES6+. That's a tremendous legacy. But continuing to develop CoffeeScript in 2026 is like maintaining a telegraph network in the age of 5G.
-
-The language works—CoffeeScript 2 outputs modern JavaScript that runs everywhere. But "works" isn't enough when the entire ecosystem has moved on. Development is a team sport, and CoffeeScript has no team left.
-
-### The Harsh Truth
-
-CoffeeScript 3 would be a technical achievement that nobody asked for, solving problems nobody has, for a community that no longer exists. The language's elegant syntax cannot overcome the brutal reality of ecosystem abandonment.
-
-The kindest thing for CoffeeScript is to recognize it as a successful historical artifact that accomplished its mission: pushing JavaScript to become better. That mission is complete. CoffeeScript won by losing—its ideas live on in modern JavaScript while the language itself can finally rest.
-
-**Building CoffeeScript 3 isn't just unnecessary—it's actively harmful to the developers who would be trapped maintaining codebases in a dead language, cut off from the vibrant, innovative JavaScript ecosystem of 2026 and beyond.**
-
----
-
-*The real question isn't "Why not CoffeeScript 3?" but "Why would anyone choose suffering when better alternatives exist?"*