Good Goddamn, Powershell Sucks!
Apparently Blogger sucks too, 'cause I can't get this picture to display at full resolution. You'll have to click to read it: 
In case you can't be bothered, powershell's remove-item crashes with
"The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."
Then cmd.exe's rd /s /q works just fine. cmd.exe.
Seriously. How. The. Fuck. Does this ship? How the fuck am I unable to delete files that the Operating System will allow me to create? When cmd.exe works? I'm sure there's a really interesting reason why this error happens. Some bizarre technical reason, or, more likely, some political tale about how people wanted to fix it, and couldn't. You know, the type of stuff that makes the daily wtf a popular site. But I don't care. Not right now.
Right now, I want Powershell to work at least as good as what it desires to replace.
I'm thinking there's a solution involving set-alias rm, but I haven't coded it yet... (probably won't either)
Subscribe