You won't see that. Even the Java plugin is going to a minimal modular distribution. E.g., it will lazily download parts of the Java library on demand when they are first used. This gets the Java plugin download down a lot, and a lot of the large parts of the library (e.g., internationalization components) are never even downloaded by most users.
I have nothing against combinators being used in applets. But it is a bit ridiculous that its included in the scala-library.jar file if we want that component to be as minimal as possible (I don't think we really care right now, applets are pretty much still dead, everything is in Flash now).
Sean
On Sat, Aug 2, 2008 at 1:35 PM, Jim McBeath
<scala@...> wrote:
I happen to be using parser combinators in this applet. I saw
another scala applet that had a pruned down scala-library that
was only about 200K. Packaging my own applet-specific version of
scala-library.jar seems like a reasonable solution for now, until
the day when the Java plug-in contains scala-library.jar.
--
Jim
On Sat, Aug 02, 2008 at 01:10:46PM +0800, Sean McDirmid wrote:
> I think we'd eventually have to split up scala-library.jar if applets
> become popular again. I mean, we already have core Scala (scala.*), and
> services (actors, parser combinators) which are definitely not used in
> every applet.
> Sean
>
> On Fri, Aug 1, 2008 at 11:21 PM, Miles Sabin <
miles@...>
> wrote:
>
> On Fri, Aug 1, 2008 at 4:18 PM, Miles Sabin <
miles@...>
> wrote:
> > I looked at various tools of this sort fairly recently, and the best
> > free and open source option I found was ProGuard,
>
> Oh, and the author provides a fairly comprehensive looking list of
> alternatives,
>
http://proguard.sourceforge.net/alternatives.html
> Cheers,
> Miles
