Skip to content

Add language-specific causes of death to scoring #10

@dotsystemsdevs

Description

@dotsystemsdevs

What

Right now `determineCauseOfDeath()` in `src/lib/scoring.ts` only has one language-specific rule (JavaScript → "Lost in dependency hell"). We should expand this to cover more languages with causes that actually fit their ecosystems.

Examples

Language Possible cause
PHP Died of PHP fatigue
Ruby Gemfile.lock never unlocked
Python Pip froze, then everything else did
Perl Nobody could read it, including the author
CoffeeScript Outlived by the thing it inspired
MATLAB License expired, so did the project
Objective-C Swift happened

These are just starting points — be creative, stay accurate.

Where to add it

`src/lib/scoring.ts` → `determineCauseOfDeath()` → add new objects to the `rules` array:

```ts
{
score: repo.language?.toLowerCase() === 'ruby' ? 5 : 0,
cause: 'Gemfile.lock never unlocked',
},
```

Acceptance criteria

  • At least 4 new languages covered
  • Causes are accurate and funny, not just mean
  • Existing tests still pass (`npm test`)
  • `npm run lint` passes

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions