On Sun, Aug 8, 2010 at 16:06, Viktor Klang <viktor.kl...@gmail.com> wrote: > this discussion is becoming more and more blurred. > There are infinitely different situations with different needs and different > constraints, there is no point in trying to argue that solution X will work > for everyone.
I think the OP fully exaggerated with the title of the thread. But I think the thing behind the Scala discussions is: Will Scala become the substitute for Java as - let's say VB.net or C#.net is (meant to be) for VB(A). Java is a very common language. And definetely when I am looking at a new language I always look at it if it can be the one and only language I need to do everything. I don't want to change language for each new project after evaluating the needs. Needs may change and then what - change the language and write everything for new? Scala of course is also a language meant to be used for everything and I think theoretically it does - just for practical still some implementations needed (in the IDE or in the tooling) - but this will come. But as we see for Google Wave - not every cool thing gets widely accepted. - We will see what the future brings. I for myself prefer Java although I am not one of those doing Java for a decade and I don't have much "legacy" Java code as most others. -- Martin Wildam http://www.google.com/profiles/mwildam -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
