Execution in the Kingdom of Nouns (2006)

Post by abc_lisper » Thu, Feb 14, 2013, 7:08 PM UTC

Roboprog wrote: post #68

abc_lisper wrote: post #61

Earlier quoted context omitted.

Just to note, I am in no way claiming Java is superior. Java is inferior in ways I think are not the ones Yegge claims. For me, these are the things Java sucks at. 1) There is no easy way to create lists or maps. Look at python; how easy it is to create a dictionary. In Java, you have to "write code" to put elements in a map. 2) Reflection is very weak. It is not type checked at compile time. You have to write a lot…

For all of its warts, Groovy really makes much of this more tolerable in an environment that readily interoperates (call either way in/out) with legacy Java code. Java file handling with dozens of classes still seems a horrific solution, like you said. I don't miss having to constantly check return codes and "errno", vs getting IOException, but I do miss the simplicity some days of "FILE *" and fopen()/popen(). (I al…

Post by vorg » Sat, Feb 16, 2013, 11:20 PM UTC

Roboprog wrote: post #68

abc_lisper wrote: post #61

Earlier quoted context omitted.

Just to note, I am in no way claiming Java is superior. Java is inferior in ways I think are not the ones Yegge claims. For me, these are the things Java sucks at. 1) There is no easy way to create lists or maps. Look at python; how easy it is to create a dictionary. In Java, you have to "write code" to put elements in a map. 2) Reflection is very weak. It is not type checked at compile time. You have to write a lot…

For all of its warts, Groovy really makes much of this more tolerable in an environment that readily interoperates (call either way in/out) with legacy Java code. Java file handling with dozens of classes still seems a horrific solution, like you said. I don't miss having to constantly check return codes and "errno", vs getting IOException, but I do miss the simplicity some days of "FILE *" and fopen()/popen(). (I al…