Some complaints also seem like a lack of experience using the language. For example

   Initialization with make behaves differently for maps and slices:

   m := make(map[int]int, 10) // capacity = 10, length = 0
   a := make([]int,       10) // capacity = 10, length = 10 (zero initialization)
   b := make([]int,    0, 10) // capacity = 10, length = 0
   So not only is there an inconsistency, the more common operation has a longer spelling.

In my experience, the two-value (explicit capacity) form of "make" is significantly _less_ common than the single-value form. Indeed, gripping through the stdlib shows "make([]T, n) is much more common than "make([]T, n, m)".

I agree that appending to "make([]T, n)" is not an uncommon mistake. But, in general, you can avoid that problem by assigning to specific indices instead of using append.

I think the place I regularly use "make([]T, 0, n)" is when I'm collecting items from a

   s := make([]K, 0, len(m))
   for k, v := range m {
       s = append(s, k
   }