Sorry, I do mean build time, proguard included for scala. Those times are on my SSD, and total build time tended to hit almost 5 minutes on my desktop with a HDD. It was very slow which furthered my aggravation when the incremental compiler goofed something b/c then I had to do a full clean and build. Switching to scala+sbt dropped those times dramatically, proguard included.
On Tue, Jul 22, 2014 at 2:23 PM, Nick Stanchenko <[email protected]> wrote: > joined macroid group so msg would go through (last didn't), but another >> thing I see come up and that's in your docs right now is slow compile times >> on large projects. I must be the only person to experience the exact >> opposite b/c I've seen that stated by a few people. >> > > First let’s make it clear, that it’s *build *time, not *compile *time, > that is the problem (due to ProGuard + dex). The whole process is very > inefficient: first we have to go through a compiled jar to find and exclude > methods. The compiler could mark the used methods from the start! Sébastien > Doeraene has implemented a similar feature for ScalaJs and told me that > stripping took around half a second (!). Next, the jar is transformed by dx > (and now dex2oat?). If only Scala had a Dalvik backend, things would be > much faster! The problem is of course that no one has both the time and the > expertise to tackle this. See > https://github.com/pfn/android-sdk-plugin/issues/68 > > One of the sole reasons I even started using scala was >> >> (a) the incremental compiler actually worked and didn't spit out random >> bad builds on me >> > (b) compilation times dropped roughly 30% (I have raw stats in some >> private emails somewhere) with a generic project conversion and then >> dropped even more, from 2.5 minutes on original java project (no proguard) >> to 45 seconds after diving in and writing proper scala. >> > > I have to say that my experience with Java is very limited, and 2.5 min > seems enormous. My 10KLOC pure Scala project incrementally builds in around > 50 sec (ProGuard cache is disabled, because... I can’t handle it). On the > other hand, that’s exactly why I try to specify the time when I say “big”, > so that other people could compare with their results and make the decision. > > >> (c) Lines of code dropped significantly, from around 20k to 12k (and >> still dropping) >> > > That’s for sure! And with some things, I can’t even imagine having to > write them in Java (which probably means I’m just bad at Java...). > > -- > You received this message because you are subscribed to the Google Groups > "scala-on-android" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "scala-on-android" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
