Thank you so much for your reply.
By the way, I realized that if we also use scala reflect instead of Paranamer, lift-json extraction will likely work in Scala REPL. This would be really handy and it's top issue in lift-json FAQ.
Additional 15 MB in every assembly is a problem, because:
- build time is worse (especially if you include upload time and do that in continuous way)
- deploying takes longer
- jvm startup time is also a bit worse
Each of this performance hit is rather a small one, but multiplying it be a huge number of machines and jvms it looks like something worth optimizing. That changed itself, decreased the total size of assemblies by about 15% (I include all of our static resources, it takes much more if I count just jars).
Moreover, I am not the only one experiencing this issue, some links to previous discussions:
[SNIP]
I see you point about scala-reflect being marked as a experimental. However, in my opinion in it its current form it's way better than scalap.
…
So in my eyes scala-reflect is fairly mature official Typesafe library, with some warning that is not as stable as rest of compiler.
I would really love to involve more in lift project, starting from that issue. I read the wiki, but it seems that it would be hard without being a committer. I haven't found any information on how to became one, but would be happy to do more coding if the community would support that change. Even if you don't share my optimization views, I believe that fixing lift-json in REPL might be interesting value proposition.
For note, I use lifts json in a non-lift project, without including the Scala compiler lib then my distribution size would fall from over 60 megs to about 45 megs, and averaging over 600k downloads a month on the slow months (over 2 million downloads on a new release month) would save me a *lot* of bandwidth, I did not even know scalas compiler could be taken out of it. I use the compiler lib for something else too but I could easily remove that dependency. Thanks for your branch of that dependency removed, as I use 2.10 I will give it a try, but I would love this merged into the main repo for mavenization purposes.
TL/DR: I have a package with Scala compiler because of lift json, fixing this would save me ~15megs per download over near a million downloads of this project per month.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
For note, I use lifts json in a non-lift project, without including the Scala compiler lib then my distribution size would fall from over 60 megs to about 45 megs, and averaging over 600k downloads a month on the slow months (over 2 million downloads on a new release month) would save me a *lot* of bandwidth, I did not even know scalas compiler could be taken out of it. I use the compiler lib for something else too but I could easily remove that dependency. Thanks for your branch of that dependency removed, as I use 2.10 I will give it a try, but I would love this merged into the main repo for mavenization purposes.
TL/DR: I have a package with Scala compiler because of lift json, fixing this would save me ~15megs per download over near a million downloads of this project per month.
--
--
Lift, the simply functional web framework: http://liftweb.net
Code: http://github.com/lift
Discussion: http://groups.google.com/group/liftweb
Stuck? Help us help you: https://www.assembla.com/wiki/show/liftweb/Posting_example_code
---
You received this message because you are subscribed to the Google Groups "Lift" group.
To unsubscribe from this group and stop receiving emails from it, send an email to liftweb+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.