Scribe vs Minion
The honest comparison. No fluff.
Why people switch from Minion
- Built on Java | higher memory footprint, slower cold start
- Not open source | can't inspect or contribute
- Dependency management is limited
- Development has slowed way down
Feature comparison
| Scribe | Minion | |
|---|---|---|
| License | MIT | Proprietary |
| Price | Free | Free |
| Runtime | Go (native) | Java |
| RAM | ~50-60 MB | Higher |
| Startup | Instant | Several seconds |
| Windows / Linux / macOS | Yes | Yes |
| Dependency detection | Automatic (metadata + description parsing) | Basic |
| Bulk updates | Yes | Yes |
| Bulk uninstall | Yes | No |
| Account needed | No | No |
| Source code | GitHub | Closed |
Switching from Minion
Nothing to migrate. Scribe reads your existing AddOns folder directly | all your installed addons, settings, and saved variables are already there.
- Download Scribe
- Open it, confirm your AddOns path
- Done. Uninstall Minion whenever you feel like it
Both can coexist on the same machine. Run them side by side until you're comfortable.
What Scribe doesn't do yet
- Backup and restore
- Addon favoriting / collections
Want something? Open an issue.