| ▲ | NamTaf 4 hours ago |
| What got removed to make this smaller? You don't just shed 97% of the size without compromises. What are those compromises and why were they made? |
|
| ▲ | semiquaver 4 hours ago | parent | next [-] |
| Your assumption that 97% of a binary isn’t usually bloat is not well-founded |
| |
| ▲ | nign 2 hours ago | parent [-] | | Your assumption that a vibecoded project with a single contributor behind it can cut 97% of the size of well established open source projects without breaking something very badly is not well founded. | | |
| ▲ | inexcf 12 minutes ago | parent [-] | | Image size isn’t a good proxy for features here. Sonarr/Radarr/Lidarr/Prowlarr are .NET, Bazarr is Python, Overseerr is Node. Each Docker image ships its own runtime and base OS layer, so a big chunk of those ~718 MB is the same kind of overhead duplicated six times. One static Go binary skips all of that. And the *arrs in my opinion really should not be different tools, each has its own indexer handling, download client integration, queue, scheduler, database, auth and web UI. Most of what each tool does completely overlaps with the others. So even more of the overhead is not necessary. |
|
|
|
| ▲ | poilcn 41 minutes ago | parent | prev | next [-] |
| Different stack This one is golang project The ones it replaces are self-contained .net core web apps which themselves bring at least 80mb runtime for hello world if not compressed |
|
| ▲ | FabCH an hour ago | parent | prev | next [-] |
| To be fair, it's an entirely different language and they had an automated test that forced the AI to keep the binary small. |
|
| ▲ | cnqso 3 hours ago | parent | prev [-] |
| It doesn't actually include Prowlarr for starters |
