> Why can't we be interested in both? I am not saying you couldn't be interested in both. Actually I am. I just wanted to keep the two things separated. This can be a questionable choice with pros and cons. I was just suggesting to try this strategy but to tag the "scala infected" thread with [scala] could work either. I am just afraid that more than the half of the threads in this mailing list could be sooner or later tagged in that way.
> From a business perspective, I don't see > a chance of getting Scala into production. Sorry, but this sounds just the point of view of a java fan. And that's exactly what I was trying to avoid by creating a different discussion group. For what it matters, Scala is already in production in a lot of enterprise level projects. > I could realistically see > companies using JDK 7 or 8 into 2020 or beyond. I see the same as much as I see lots of cobol programmers in 2010 still. What should that mean? > Keep the scala and groovy discussions. Just loose the 'fan boy' mentality. I will try to. But once again let me notice that often java fan boy seems to be the most intransigent ones. > So what if I have to write twice as much code. My employer doesn't care if I > write 100 or 1000 lines of code to do something. All they care about is > whether it works properly and did it get done on time so they can get it to > market. That is where the paycheck is and our job is to deliver. Indeed your customers don't care of the languages and technologies you use. I wrote exactly the same in a former email. They don't care but you should anyway. If you have the half of LOC you will have the half of bugs and maintenance costs. As stated by Antoine de Saint-Exupéry: "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to remove" My 2 cents, Mario -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
