|
|
|
|
|
|
by threeseed
4147 days ago
|
|
|
I find your and the parent's arguments really interesting. For me Go reminds me so much of Java 1. And it seems to be getting pulled by the community in the enterprise Java direction e.g. generics, annotations, dependency injection, broad frameworks and the simple, tightly focused tooling direction. |
|
|
* Go had annotations since pretty much day 1. Look at the annotations for JSON serialization, for example.
* Generics is something that Go is probably not getting. It's just become a troll topic at this point since everything that could be said about this topic, has been said.
* Dependency injection is something that Go isn't getting. It's a Java solution for a Java problem. Create well-thought out code with clean interfaces and unit tests... problem solved.
* Broad frameworks: it's just not going to happen. As a lot of other commenters have said, Go just doesn't support the level of abstraction that you need to create a FactoryPatternPatternStrategy. And that is a good thing, in my opinion.
* Tooling: I have no idea what you mean really. Java's tooling is hardly "simple" or "tightly focused" (have you ever USED Maven?) and Go's community didn't "pull" the golang authors to create simple tools... they've been simple and focused since day one.