> I keep hearing this, but in years of shipping Alpine based images into prod the problems never materialized. Postgres has very subtly different sort ordering

> I keep hearing this, but in years of shipping Alpine based images into prod the problems never materialized. Postgres has very subtly different sort ordering when we use the alpine based images. That the dev trying the upgrade locally happened to pick alpine got what should have been a very simple couple person-days upgrade backlogged. And drawn out & stumbled over. Multiple people wading through a long series of changelogs. We eventually figured out what was going on, but it was a miserable long soggy sad trudge to get ourselves back on track. All because someone used a not-so-standard library. Musl causes a more regular pain of node add-ons needing to be specially compiled, but at least we typically see these coming. Time lost, but at least predictable time lost. One other gripe: musl also is not designed for server workloads at all. It's designed for space efficiency & small systems. Sometimes memory can be a dominant cost or a crucial factor for online services, but for most workloads, you are probably misoptimizing your system by misapplying what was intended as a niche standard library to your system.