Reason #35276 why I stopped using eclipse.
That totally has nothing to do with eclipse. It's the fault of the plugins writers.
Mattheus, are you doing game programming Scala or other things? I keep flipping back and forth between doing things in Scala and Java (and wasting a lot of time in the process). If you've been using Scala for game dev, how have you found it?
Hm. Thing is: I am still learning scala.
I am a very special programming person when it comes to the languages I like and know.
Everything started with my brother getting intrested in programming. He started with java. About 4 years later I started programming too.
And I also started with Java too.
The special thing now is: My brother hates java at this point. He is now a non-imperative functional programmer (scheme (with guile), you know, this language with all these ()()()()()).
My brother showed me scheme. I really have to say: It's a simple language and I really have to say that I like it. It doesn't even seem to be very slow...
But I kept with java. (I'm still loving OOP (scheme can give you OOP with CLOS... but I still don't like it

(because of non-variable access (which would be instanceOfObject.methodFromThatInstance(), wheras in CLOS it would be a function call to "methodFromThatInstance" with the argument "instanceOfObject"...)))
So now I found Scala. I'm still learning as I said. But there are very much things I like (scala seems to be a functional-extension and improved version to java), for example giving functions as parameters. But I still stay with writing things the "imerative" way. So I don't recreate a vector each time I add values to my given vector (I'm speaking of mathematical vectors (think of Vector2f...)) and I still use classes much more than anything else.
The bad thing with scala is: It does not have one thing from all the functional programming languages:
Take as an example (a OOP AND functional language) javascript. I learned it within a day. Or about that time (okey. I did not learn scala that itensive, but I'm at scala since already more then a week).
Next example comes from the lisp-corner: scheme. I didn't learn it within a day. But scheme is simple from the syntax view: a "(" and a closing ")" will make the computer compute what is inside. Then: the first word after the "(" is something describing what the computer has to do (the funciton name) and the rest which come before the "(" is closed by a ")" are the arguments. For example:
(define x 100).
define = define something
define takes a name as the first argument.
and what to assign the value to as the second argument.
Further:
(define x (* 500 500))
(I wont explain this one...)
And in scala you have : Unit = {} and => and <- and ## and () => Unit and all this stuff :/ (I didn't even get my old beloved for loops ?!?!

and it really seems to be hard if you can't write a for loop without googling how to do that...)
So scala is really a hard language to learn, but I'm very sure, that scala is a very good language. It combines soooo much features and that from the beginning on. What the people behind Java are doing now, is they are putting everything which is missing in Java into it. (lambdas, ...)
So: IMO Scala is awesome

(but hard to learn)
Anyway, Scala is certainly a nicer language than Java no matter what kind of program you are writing.
Hehe... have fun with this statement in a java forum
