The point of a Digital Asset Manager isn't just organizing files. Every OS has a native method of doing that. The reason we need a DAM is to facilitate non-destructive editing. This is where LR and Aperture (rip) excelled, and why people latched on to them. Before LR there was Bridge, which was good for the time but you could easily stack up many GBs of "versions" that shared 99% of the same bits. True DAMs solved that problem by storing master files and saving versions as editing instructions to be applied on export. Aperture was the king of DAM for photography, and happily stored whatever files you threw at it. It could even handle multilayered psd files with ease. C1P is pretty good but lacks Aperture's stacking and album features, plus it's slow as molasses with large libraries. I can't speak much to LR anymore since I haven't used it in ages.
The other critical feature of a DAM is culling. That means ratings and filters. This is where amateur applications like Photos fall short. You can "love" a photo, but it won't do star ratings (honestly I would have used Photos if not for this lacking feature because the plugin implementation is pretty decent).
I think it's really difficult to invent a method of storing any and every type of file while still allowing for a roundtrip non-destructive workflow. It's not impossible, but there will always be compromise.