2 ms·
Er...[if you have the misfortune of being paid to work in Java] they remove a pile of type-casting cruft and make code more useful to large and/or transient tea
by gills 16y ago
Er...[if you have the misfortune of being paid to work in Java] they remove a pile of type-casting cruft and make code more useful to large and/or transient teams.
The author conveniently glosses over the type-casting from pre-generics Java and instead compares to Ruby. Duh...of course Ruby is a cleaner read. But compare learning a new API:
// pretty evil
List<Thing> getTheThings();
// really evil
List getTheThings();
Or iteration:
// pretty evil
for (Thing t: getTheThings()) {...}
// kill me now
for (Iterator it = getTheThings().iterator(); it.hasNext()) {
Thing t = (Thing) it.next();
...
}