The following things are targets for which we all need the same focus. Since 
they kind of rule eachother out, we have give them a prio-order. For instance, 
making it more user-friendly might cause extra code, which will make the jar 
grow.

In any order I come up with the following (maybe I'm still missing some...):

* small jar-size

* user-friendly

* closer to java-api where possible

* compact/redundant code vs. inheritance/delegating methods

 

Maybe there are some historical facts I'm not aware of, so please let me know.

 

- Robert

 

 

 
                                          

Reply via email to