> In my experience this kind of gatekeeping eventually breaks down due to deadlines and similar. I don't disagree. That's why I said the sweet spot is much clo

> In my experience this kind of gatekeeping eventually breaks down due to deadlines and similar. I don't disagree. That's why I said the sweet spot is much closer to Java/C#/Kotlin. > But I have not noticed that it's too often That's the problem though. Those silent difficult to detect bugs are what affect reliability and safety. With exceptions, you're going to have to explicitly ignore them, whereas with golang errors, it's much easier to misuse them. Not to mention the fact that golang errors are basically strings, which makes dealing with them very error prone. > Hard to compare with an anecdote like that, I just haven't heard much complaints regarding compile times, if anything the opposite, and certainly not that it's a significant problem in a pros/cons comparison. My guess is that most people don't use golang for large projects, and few who do don't care about the long compile times.