Yes, in go these things have solutions. Maybe not the best ones we can have, but there are ways to approach the problems beyond just giving up.
1 - Most editors automatically support that. I wouldn't say being forced to follow a certain code convention is bad, but it understandable that it may bother some people.
2 - You can still the code-reuse features of inheritance by using embedded structures with methods attached to them.
3 - There are many solutions which solve the problem without needing to commit the vendor directory to git like `glide`.
1 - Most editors automatically support that. I wouldn't say being forced to follow a certain code convention is bad, but it understandable that it may bother some people.
2 - You can still the code-reuse features of inheritance by using embedded structures with methods attached to them.
3 - There are many solutions which solve the problem without needing to commit the vendor directory to git like `glide`.