I understand your argument. I think it relies on your earlier statement: "The fact the the path is stored as a string is an implementation detail."

This statement reminds me of the term "architecture astronaut". Pathlib builds a cool architecture over the concept of paths. But landing back in reality, all paths are strings, aren't they? On any OS, even looking at esoteric things such as UNC paths on Windows, they're all eventually strings and are treated by most tools as just strings.

If I'm missing any edge cases, let me know. But otherwise I think it's okay to look at `Path` as a string with bells and whistles.