ok, I guess the reason they did it was to distinguish the Documents under Libraries from the folder under the user's ~? That kinda makes sense, but does .net grok Libraries, or does dealing with them mean dealing with Win32 and shell namespaces and PIDLs?
it would be nice if Powershell could deal with Libraries transparently, but cmd.exe couldn't. anything that forces people to stop using cmd and start using Powershell is good.