"Only 1.1M" Why do I care? Is this framework designed for embedded systems or mobile apps? Smaller is better, but one MB vs 10 MB makes no difference for me as a guy writing server-side Java.
I suppose it makes a difference when it comes to getting your local dev environment set up. Plus, you might be able to get away with doing continuous integration that downloads all its dependencies every time it runs.
I'll trade a 1% reduction in implementation time for 10x the jar file sizes. I'll take "lighter" in terms of API surface area, memory/CPU usage, etc. though.
