🚀 go-pugleaf

>Property files are the
>way to go, as Rich pointed out.


I spoke to someone who has been developing in Java for two years (yes, he's
a pioneer). He definitely prefers to use a serialized singleton class and
save/restore the data using object I/O. He pointed out that the Properties
class predates serialization and would probably have been implemented
differently had serialization been defined first. For my money, the only
advantage I can see in using the Properties class instead of serialization
is the data is saved in textual form and can be edited outside of the
program. Beyond that, I would tend to lean to serialization I suspect
because it would be much more straightforward to use...