> so there is no need to delegate a choice to the application Until there is a need. Can you see the future? Do you know for a fact that there will never, ever

> so there is no need to delegate a choice to the application Until there is a need. Can you see the future? Do you know for a fact that there will never, ever be a single edge case where being able to change the order might be beneficial? This is nanny-state moral-idealist development. It's one thing to pick defaults. It's another to choose a design decision that literally screws people over, because either you thought you were smarter than everyone, or you didn't care if you screwed anyone over. What if a cipher suite turns out to be broken? Just like any other vulnerability, it will be fixed in security release for all supported Go versions Ah. So the millions of statically-compiled Go apps just all need to be recompiled, for every version and platform they were ever released for, and re-downloaded. For supported Go versions. Why not make TLS 1.3 cipher suites configurable? Conversely, there is no tradeoff to make with TLS 1.3, as all its cipher suites provide strong security Until a cipher suite turns out to be broken. Like they pointed out in the first question.