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. More.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.