each had major existing workflow in perl. one needed to fetch data only available with java api, other needed algorithm only with java api.
On 7/15/13, John Redford <[email protected]> wrote: > > David Larochelle wrote: >> >> I've also posted the slides to my blog at > http://blogs.law.harvard.edu/dlarochelle/2013/07/14/inlinejava-using-java-wi > th-perl/ >> > > There is a question that the slides don't address which I am curious about > -- why didn't you just use Java & Java-based languages? The slides make a > fine argument for using Java, but little or none for using Perl with Java > -- > using Perl is apparently taken for granted, despite all the oddities of > calling between them. Given that the calling cost from JVM-based dynamic > languages (e.g. Xtend, Groovy, Jython, et al) is virtually free, why not > use > them instead of Perl? > > > > > _______________________________________________ > Boston-pm mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/boston-pm > -- Bill @n1vux [email protected] _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
