Honestly I really don't get people who are obsessed with this. Static vs dynamic? That matters A LOT! Error handling style? Very important. Expression based vs statement based? Now you are talking.<p>but whether a type is before or after the name of a variable? Come one man.,,
FTA: “In C, the following declares x to be a pointer, but (surprisingly at first!) y to be a normal integer:<p><pre><code> int* x, y;
</code></pre>
Whereas the equivalent in Go does what you’d expect, declaring both to be pointers:<p><pre><code> var x, y *int</code></pre>
”*<p>I don’t see how that’s an argument in favour of <i>`age int`</i> over <i>`int age`</i>. Both C could easily have picked the alternative semantics. Go could have, too:<p><pre><code> var x*, y* int; // two pointers
var x, y* int; // x is an int, y a pointer to int
</code></pre>
or<p><pre><code> var *x, *y int; // two pointers
var x, *y int; // x is an int, y a pointer to int</code></pre>
type name ....is better, any other arrangement including adding stupid symbols like : ...is just retarded alot of retarded people around these days alot of them took the vax.. because they are retarded.