3 Dominant Themes
1. The “Go kids” narrative is a straw‑man
“The Go \"kids\" are famous for, among other things, being industry leaders 30 years ago.” — gowld
“Between this and the IPv6 zone identifier issue, it feels like there's a trend of commenters more or less assuming Go is doing the wrong thing when it's actually following the standards/best practices more correctly than average.” — jchw
2. Go’s stricter X.509 string‑comparison stance
“Go requires the Issuer and Subject to be byte‑for‑byte equal.” — agwa
“The reason it doesn’t validate in Go is that the Subject field in the CA certificate uses a different string encoding than the Issuer field in the leaf certificate, so the fields are not byte‑for‑byte equal.” — agwa
3. Mis‑perception that Chrome/OpenSSL are “right” while Go is the outlier
“Most people accessing a site are likely not using Golang and are using Chrome. Thus Chrome is assumed right and Go is the one that's the outlier.” — fragmede
“That's a different point, this particular thread is actually about a behavior that Chrome/OpenSSL/etc. have that is actually somewhat undesirable due to being complex and error prone.” — jchw All quotations are taken verbatim from the discussion.