Quote:
Originally Posted by Super Aids
Sounds an awful lot like Java's type-erasure.
|
Except it's worse - since even shitty Java actually
has generics.
If you want to compare it to Java, it's more like using the pre-generics HashMap in Java:
Code:
public static void goSucks() {
Map map = new HashMap();
map.put(1, "One");
map.put(2, "Two");
String one = (String) map.get(1);
}
instead of the safer, more modern, type-safe, generic approach:
Code:
public static void evenJavaIsABillionTimesBetterThanGo() {
Map<Integer, String> map = new HashMap<>();
map.put(1, "One");
map.put(2, "Two");
String one = map.get(1);
}
... but apparently, the braindead Go language developers/creators don't mind being stuck in the 70s - well, Java has only had generics since 2004, but C++ had templates in the mid 80s, Ada had generics in 83, ML had it in fucking 73.
Then again, Rob Pike, one of the dumbass creators of Go, even said himself:
Quote:
|
The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.
|
- Basically saying: "Our language is made to be utter garbage, because it's going to be used by garbage programmers". What a joke.