For Go: 1. Exports from packages are to be defined with a Capital letter. To me, that is very hard to read. An explicit export statement is way better, if verb

For Go: 1. Exports from packages are to be defined with a Capital letter. To me, that is very hard to read. An explicit export statement is way better, if verbose. 2. Type declarations after variable (x int, y int), to me personally, is hard to read. Now I know a lot of people are fine with it, so this is a personal thing for me. 3. Multiple return values syntax is terrible. func split(sum int) (x, y int) { x = sum * 4 / 9 y = sum - x return } In this function, the sum is the input and x & y are outputs. The syntax seems weird to be. This also is a personal gripe. 4. Variable declarations can be var i, j int = 1,2 AND k:= 3 with implicit typing. To me this is a bad design, with various programmers choosing different methods to declare and initialize. Leads to a lot of cognitive overhead to read code, especially on large open source projects. Why not make it explicit to declare types? Sure, it's a bit of more work for the programmer, but in the long run, that bit of more initial work will save a lot of downstream confusion and frustrations. 5. Constants cannot be declared using := syntax. I am sure there is a valid reason for it, but assignment in the language for now is = , := and those can and cannot be used in various places. That is confusing. 6. For loop has no parenthesis for the loop initialization but needs {} for the loop blocks. This is really stupid. Personally, for(i:=0,i<100;i++) {} is a concise syntax and looks pleasing and readable. 7. To complicate it further the initialization and post statements are optional // This is a valid for loop in Go sum := 1 for ; sum<1000; { sum = sum + 1 } Isn't that confusing in itself. Sure, we don't have to write a loop that way, but some junior developer is going to write it anyway, and it muddles up the code for sure. 8. From the official Go Docs "At that point you can drop the semicolons: C's while is spelled for in Go" // This is a ALSO valid for loop in Go sum := 1 for sum<1000 { sum = sum + 1 } yay. 9. And then there is this gem in the "if" statement. if v := math.Pow(x, n); v < lim { return v } Yes, you can write an optional initial statement before the if condition. All this for what? So you save one extra line in the code? Sorry, the beards got too long and too tangled up for whoever came up with this idea. 10. Also, the initial statement you saw just after the if statement, the variable "v" is available in the scope of else/if and else statement blocks. But not outside the if/else scope. Yay, another way to confuse code readers. 10. What is up with the defer keyword to defer function calls until the "surrounding function returns". There are many more, but I think I have made it clear why, personally, Go is off putting. edit : Changed format a bit.