At the risk of taking this thread too far afield: Well there's always room for personal opinion for which tools you use. Some people may prefer a Bosch driver over a Makita and others will happily pay for the Festool. Any of them will put screws in boards. But some hands will prefer different drivers for various reasons. Nothing wrong with that.
Personally, as a programming language, I don't care for Java. I've written some code in it and will undoubtedly write more. But, IMO, it's difficult to use well if you aren't using it all the time. OTOH, for those who do use it all the time it's probably second nature and know that class X is better than class Y for the particular problem at hand, even though both do very similar things. For those people, Java is probably a fine choice. But the concept of the JVM to enable portability across a wide range of platforms and architectures is a good one. And from the mainframe perspective, getting work on the zAAPs is potentially good. And as it turns out Java6 contains Rhino, so I can write code in one of my favorite languages (JavaScript) on the mainframe. That is another benefit of the JVM: if you have a language that runs in the JVM, it should run on the mainframe. So if Groovy feels right in your hands, I believe you should be able to use that on the mainframe. > I really, really don't understand objections to particular programming > languages. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
