On far to many occasions in the past in Puppyland, there have been browser concerns raised to Puppy development and, sometimes, by development. Much of the discussion is along the lines of personal preferences.Sometimes its along the lines of download size, sometimes its about processor use, sometimes about RAM use, sometimes about memory use (yes, RAM and memory are distinct), sometimes about the time to start to the desktop when first used, sometimes ... and so on and so on.
To provide both developers and users a good manner of measurement, we need some way of looking at browsers better than the sometimes emotional methods we've used in the past.
So I ask
- Can anyone of this community suggest or provide a recommendation of a UTILITY we can use to compare browser operations in any given PUPPY? OR,
- is there a way to use an existing Puppy utility to get measurement information on browser impact on the system?
- And, What should the criterion be for the decision process for an OOTB browser solution in a stock-standard PUP (in other words, does measurements weigh in the process of having a browser in PUPs)?
