It can’t be that it’s going to take more time translating Python code to Java than the time to code the algorithm in Python first.
I started converting the algorithm contained in a public method with two arrays of char as arguments but when I decided to switch to java.lang.String it occured me that I had to change a lot of things on the inside (first absurd thing):
- All this enforced types thing sucks. I know templates are there now in Java but they don’t really resolve the problem of genericness and also I don’t have Java 1.5 at school, so forget them.
- It’s not kinda possible that arrays have a “length” public member and String(s) have a method. This is inconsistency of a language. And to me sucks.
- I find really awkward the thing that with arrays I can use “arr[i]” indexing notation but String items have to accessed with “charAt”. This really sucks
- It’s not possible that a 2006 language carries on with a stupid problem such as the coupling of classes and name of files. It sucks to have to remember to change the name of the classes or change the name of the file. Shame on you Java.
- Staticness and compilation separated from execution it’s really boring.
- Last but not least. What’s wrong with you Java-guys loving so much this everything-boxed-in-a-class thing? I want classes when I need classes. No way I’m going back to the Java world domination front. Python is a freedom language. No fuss.
So Java really sucks to me now. I love freedom languages. I want to be free to concentrate on what I have to write in my Emacs not how to write it or counting the semi-colons or the braces. No no no. Really thank you Guido for coming up with this lovely language.

