About

Vividly I recollect the day when I encountered the Java programming language.

It was a simple language, quite a contrast to the languages I knew at the time. Some where powerful, if bloated and complex monsters like C++. Others where simple, but you could not do everything you wanted to do.

Who! What a cool language. Really fun, really productive.

As years passed by, I began to realize I was doing the same tasks over and over again. Those tasks became tedious and boring. Nowadays they often make me feel tired. Popular frameworks like EJB 2 did not help, either – you could do virtually everything with them, but they suffered from a lack of simplicity. Quite the contrary: they a a certain tendency to bloat my code even worse.

Then I met Groovy.

Suddenly I realized what I was suffering from. Java´s great virtue – simplicity – had gone lost during its evolution. Sacrificing Java compatibility allowed the Groovy language designers to create a simple language. Well, maybe the language is not simple. But it allows you to express your thoughts in a simple, concise manner. Being able to write simple-to-understand algorithms is something I value more than simplicity of language design.

Quite a cool language, making me enthusiastic again. But – not quite enthusiastic as Java when I knew it.

Problem was, I met the Scala programming language at the same time. And I liked it even more than Groovy. Obviously the language designer looked carefully at the pros and cons of many programming languages. Than they designed a simple language that allows you to express your thought in a simple, concise way. So Scala is even better than Groovy. If only… well, Scala makes a lot of things different than Java. So you have to learn it before getting productive. Groovy´s approach – 99% Java compatibility – is quite a clever trick. Really seductive.

All right, I admit it: concerning to programming languages I a promiscuous. I try to choose the language suitable to the task at hand. And thats all right, this is the way it ought to be.

Reading this, you may have noticed how much fun programming is to me. This blog is dedicated to share my excitement with you.

Enjoy!

3 thoughts on “About

  1. Tari Ikzda

    Good day,I really like studying through your website, I wished to leave a bit remark to support you and want you a very good continuation. Wishing you the most beneficial of luck for all your blogging efforts.

    Reply
  2. Hagar Kinkonnen

    I fall in your blog when I’m searching for “ILAsm equivalent for JVM”.

    My experience is just the opposite as yours.

    As an Assembly, C, C++ developer, when I first meet Java I was disappointed. Bad tools. One simple function must be encapsulated in a class (what I call OOF – Object-Oriented Fundamentalism), and the “Write Once Run Everywhere” I read as “Run Everywhere Only the Least Common Denominator.
    Not to mention that Java was slooooooooooooooowwwwwwwwwwww !
    Building a GUI app in Delphi or even VB was miles ahead of Java (besides the horrendous look and feel of Swing)

    In one phrase: For me Java was the first wide used language I dislike entirely.

    Then as you expect, for me Groovy didn’t change the scenario and only Scala change a bit, because is a powerful language (unfortunetly still is a JVM-dependent one).

    Cheers

    Reply
    1. Stephan Rauh Post author

      Funny thing is I can even understand most of your points :). As for the Java performance: this has improved a lot over time. Is performance (or the lack of it) still an issue to you?

      Reply

Leave a Reply

Your email address will not be published.