Thanks for the update James.
It's more clear :)
Regards
JB
On 07/08/2011 01:27 PM, James Strachan wrote:
On 8 July 2011 11:29, Jean-Baptiste Onofré<j...@nanthrax.net> wrote:
James,
I found this blog:
http://kotek.net/blog/scala_problems
WDYT ?
Most of the issues are old (e.g. old versions of scala kept breaking
bytecode compatibility, something OSGi can help you with anyway) or
tooling issues. See the comments - e.g. use SBT / FSC option in your
IDE. I use IDEA with Scala with FST on and its pretty fast and snappy.
Using SBT in incremental compile/test mode on 0.10 is now *much
faster* than using maven and java :). As you change a line of code in
your IDE everything recompiles& reruns really quickly.
Especially around the size of the jar.
Doesn't it in "opposition" with the OSGi granularity ?
Am not really sure if the exact size of a jar file is much of a
concern in the grand scheme of things; it certainly doesn't affect
granularity at least. That being said, sure Scala uses more classes in
the generated bytecode (as does Java 8's closures& java 4's inner
classes), but then the Scala library replaces a ton of boilerplate
bytecode operations you have to do in Java for doing
loops/mapping/transforming/filtering of code so its probably a case
that you use much less actual code and less helper classes (often
copied randomly from project to project) and libraries (google
collections v common collections v guava v all the other java
libraries attempting to make collections more palatable in Java).
Though if you're ever worried about jar sizes for Scala or Java,
there's always ProGuard to trim dead code.
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
