I wasn’t making an argument about making it less convenient to reduce use. Although I do think that can be a good way to reduce something’s use. ie. if there’s something undesirable but necessary for a programming language, I think there could be some value in making those things non-trivial to use. Consider mutable state in Haskell for example, it exists but I believe it’s more difficult to use than it would be in Kotlin. Kotlin has no opinion about whether developers should use mutable values, but does have an opinion about mutable collections.