Why not having a single Jest package? Why does Jest use that many packages?
Obviously including and searching many packages is ugly and inefficient. However, Jest currently uses many packages (jam.vector.*; jam.operator.*; etc). I will reduce the number of packages for standard classes in the future. However, controversial or prototype classes I will contain in individual packages so that they can easily be exchanged, left out, or deinstalled. I believe this modular approach will make Jest more attractive to more users. At this early development stage almost all classes are controversial and prototypes. Consequently, I have many packages. As these packages mature I will unite them to bigger bins. Additionally, I believe in reproducible research (for more information visit the corresponding SEP web page). In my current design a research project and its document map into individual Java packages. I will explain this soon somewhere else.
Related Questions
- The MiniTimer packages have a set amount of accessories already included. Does that mean I cant add any more products to the package?
- Can the individual products contained inside the iProfit eBook Package be included in other packages, or membership sites?
- Why not having a single Jest package? Why does Jest use that many packages?
