naming logic

[metagn]

The holo- prefix is good for 2 things:

• prevents me from having to come up with a unique name for libraries that are too general to avoid conflicts with other people's libraries
• clearly identifies what the package does and where it is from in the name itself

Both of these are to reduce the amount of work I have to do. Otherwise if I have a perfectly good name already there is no reason to change it.

Edit: I just renamed holo-map, I think the "holo-" prefixes should only stay if the library is preceded by its purpose, i.e. JSON and pattern matching are already existing specifications and their libraries are just their implementations under this organization. Otherwise it can serve as a codename until I come up with a better name, because otherwise the prefix is just noise and doesn't serve a purpose.