May 18th, 2004, 11:51 pm
I think you're way out of date on those 'facts'. I'm not talking about projects that people are trying to do, I'm talking about production systems that are currently managing millions of $ a day. The only time I see people fail projects in java is when they hire a non-java programmer and try to train them. It's not a scripting language! You wouldn't hire a perl guy to write C++! Java is good for some things, and complements C++ very nicely, but that doesn't mean that it's 'easy' compared to hard C++.And swing is _not_ too slow to run an interface in. A badly written interface on a 5 year-old computer might be clunky, but interfaces at our shop respond instantly. The only delays are when there is data being retrieved, and even that is only noticeable to our London users.And what's so complex about EJB? And there is nothing wrong with the vendor implementations that I know of. We're using it to manage our trade processing system. It's pretty straightforward, you just make a class with the functions you want, create a couple of interfaces, and use some xml to control the properties. (it's really nice to be able to control the database transactions and map the properties to sql with xml).As for 'losing portability' by using jni, it's much easier to rewrite only a small percentage of your code. That's the point. I used jni from a trade/order screen so that the bond info could be auto-retrieved from bloomberg using their excel addin. I only had to write a very small wrapper around their COM object, and everything else is in java. I didn't want to write the whole thing in C++, and it would have sucked to do so. The trade screen is also used on unix, but that feature isn't available. And 'the release curve'??? Don't get me started on the release curve. If you take it upon yourself to use the latest release of everything, it's your own fault. Perl goes through revisions that make some old code completely obselete. Microsoft is the worst offender, I used to be a certified MS developer, but my certification means nothing, as OLE/Open Doc, isn't really used on a high level anymore. Maybe I should switch to COM...I mean COM+...oh, sorry, that should be ActiveX...oh wait, let's release something called .Net and get everyone to try it out a few years before we actually implement it...Anyway, I've gone pretty far off topic, please excuse. I'm pretty opinionated on the matter. I program in a lot of languages and use a lot of tools, but I feel like people have something against java, which in my experience can be extremely useful. Perhaps it's because of the way some in academia have called it a panacea. It's not! But it's undeniably useful.