db-derby-user mailing list archives

> As you increase the size of the footprint, you make it harder to embed. 
> And as you add features, you are increasing the size of the footprint.

True.

Although, I was extremely happy to see that after a year of development,
Derby had hardly changed in size at all:
  - 10.2: derby.jar was 2,250,000 bytes
  - 10.3: derby.jar was 2,330,000 bytes

That's 3.5% growth in jar file size in 1 year.

thanks,

bryan