All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

(I don't really even know what Camelbones is, but) I was wondering if you use Algorithm::BinPack [cpan.org] for that. Your kind of application is even mentioned in the synopsis (s/CD/DVD/) of that module.

Well, it might or might not yet be a "first class citizen [mail-archive.com]" (which I mean to take "ships with the development tools"). However, you're right; unlike Leon's examples, there is a Cocoa bridge. I put that down to the fact that Sherm Pendley's worked for years on CamelBones with little or no reward, but at least some encouragement.

I suspect the answer to Leon's original question is a combination of "nobody wants to do it", "nobody wants it" and "the Perl world is too insular".

Perl already runs more places I care about than Java does, so to me, porting Perl to the JVM is an extravagant waste of time. Worse still, forcing Perl to be performant on the JVM would doubtless require language changes. Witness the recent trend of JRuby toward not implementing things because they're "too slow" or "too hard." I expect JRuby will either languish in obsolescence like JPython, or become a separate language competing with actual Ruby.

That's a good point. My gut tells me the Java programmers who want to be able to use an easier language, but still interface with the Java libraries, will stick with JRuby. The rest will move over to Ruby 2.0.

I think that's a bit harsh. I personally have no problem with the term "MRI" since there are now multiple implementations (JRuby, IronRuby, Rubinius), and I don't use any of them.

Performance may be an issue, but I think a much bigger issue for JRuby will be memory and cpu consumption. I don't know that it's solveable with the JVM, either. Then again, most Java programmers have never given a damn about apps like Weblogic sucking the life out of their systems, so they probably won't care if JRuby does it, t