IMO, Java advantage is that of being a standard de-facto, with mature tools, infrastructure and other things. I'm sure, there are many cool toys out there (git was a cool toy once, and SVN is still a standard de-facto in many places), but ease of use of OpenNLP (standard Java without excessive dependencies + maven) is an enormous advantage of OpenNLP in most of my use cases.
Aliaksandr P.S. The link is a nice collection of material! On Thu, Dec 29, 2011 at 6:27 PM, Jason Baldridge <[email protected]>wrote: > I'd really like to use Scala in the opennlp.ml rewrite, for reasons I've > already stated on the list. My thinking on this is to do the first > reorganization for opennlp.ml in pure Java, make a release, and then > starting mixing in Scala. I've been happily mixing Scala and Java on a > number of projects without much fuss. However, I do so in the context of > using SBT (simple build tool), rather than maven (SBT can read Maven > declarations, FWIW). It is quite straightforward to use, and I'm now using > Eclipse with the Scala IDE for Eclipse to build Java/Scala projects - so it > should be straightforward for others to get up and running with it. > > I'd be interested in hearing whether anyone has any particular concerns or > objections about this plan. Also interested in hearing whether anyone is > particularly keen on the use of Scala. > > BTW, if you haven't seen much of Scala before, I have some very gentle > introductions (aimed at first time programmers) for getting started with it > on my blog. You can find links to the posts, plus to lots of other > resources here: > > http://icl-f11.utcompling.com/links > > -- > Jason Baldridge > Associate Professor, Department of Linguistics > The University of Texas at Austin > http://www.jasonbaldridge.com > http://twitter.com/jasonbaldridge >
