You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rarely do I disagree with decisions made by team V, but this is such. Particularly, as this is a user facing change. This is also related to the "import()" grouping removal as well, (16083). I'm very sympathetic to the developer perspective, but I think it can hurt to ignore user conveniences. Especially when the language gets compared to its competition. The little differences and conveniences can add up and in ways that experienced developers might not see because they are focused on different things.
Reasons why I disagree with removing groupings:
1) Removing conveniences that already existed in V
The change is a removal of a convenience versus adding a new benefit to users. It means that those already using V will notice it. Thus it can be viewed by various users as a step backwards (though tiny), not forwards.
Now, users must repeatedly type "const" and "import" over and over. For possibly fast typing developers used to dealing with thousands of lines of code, this can seem very minor. However, there is a wider category of new and casual programmers that are or will be using the language that might think about or look at this differently.
2) Groupings exist in Go
Regardless of how we might feel about it, that will be an obvious comparison. Removing conveniences in V, still means they exist in the competition. Just as various little things can tip the "nod" in favor of V, such little things can flip the other way too. Perhaps it's something to be mindful of.
3) Not totally buying into the grep argument that was made
You can use regular expressions to capture the constants between "()" and left of "=". If vfmt is being used to convert these, that means they can be clearly identified.
Of course in the greater scheme of things, I totally agree this is very minor or trivial. Still, the little things can add up and of the opinion that user convenience should be kept firmly in mind too.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Rarely do I disagree with decisions made by team V, but this is such. Particularly, as this is a user facing change. This is also related to the "import()" grouping removal as well, (16083). I'm very sympathetic to the developer perspective, but I think it can hurt to ignore user conveniences. Especially when the language gets compared to its competition. The little differences and conveniences can add up and in ways that experienced developers might not see because they are focused on different things.
Reasons why I disagree with removing groupings:
1) Removing conveniences that already existed in V
The change is a removal of a convenience versus adding a new benefit to users. It means that those already using V will notice it. Thus it can be viewed by various users as a step backwards (though tiny), not forwards.
Now, users must repeatedly type "const" and "import" over and over. For possibly fast typing developers used to dealing with thousands of lines of code, this can seem very minor. However, there is a wider category of new and casual programmers that are or will be using the language that might think about or look at this differently.
2) Groupings exist in Go
Regardless of how we might feel about it, that will be an obvious comparison. Removing conveniences in V, still means they exist in the competition. Just as various little things can tip the "nod" in favor of V, such little things can flip the other way too. Perhaps it's something to be mindful of.
3) Not totally buying into the grep argument that was made
You can use regular expressions to capture the constants between "()" and left of "=". If vfmt is being used to convert these, that means they can be clearly identified.
Of course in the greater scheme of things, I totally agree this is very minor or trivial. Still, the little things can add up and of the opinion that user convenience should be kept firmly in mind too.
Beta Was this translation helpful? Give feedback.
All reactions