The consequences of the first steps

Some people say that the first impression is decisive, and if it is true I must have been trully disappointed with Java.

Actually I have been.

I came from the Microsoft C# edge and by far I’m not judging their way of explaining things easier, but the way Java keep forcing you to dirty your hands with silly repetitive codes and the way the community say to you “If you don’t like, go back to VB” help you when you try to explain your doubts is not the easiest way of hearing a Hello.

Well, studying Java as a first language is not easy at all, no matter the community is big or not you will have to develop everything, at least the majority with the standard API, from the ground, and for people that aren’t even familiarized with the language words and sintax you can raise this difficult a bit. To prove it you only have to remove the dust from your memories and try to remember the most terrifying pieces of code you saw when you were learning to understand what a OO program could be.

For the next posts I will explain more detailed some of these critical points of difficult:

class HelloWorld {  
    private int foo;
    private String bar;
    public static void main(String args[]){
        System.out.println("Hello World!");
    }
}

1. You’re forced to program Object Oriented from the very first start

2. The way you create attributes accessors are confusing, polute your code and dodgy

3. Primitive types are warps for OOP.

4. You don’t send messages for an object, you call methods of them.