But with bash you can just start typing text. No need to look up obscure command system and object names if they only thing you want to do is get a list of all files matching a pattern.
You must be one of those people who wonders why foreigners speak foreign languages when English is so much easier to learn! (Even our children can do it) Bash is not magically easier than PowerShell for someone who only uses it twice a year. In fact, I would say that PowerShell is easier because it has a lot of built-in aliases to make it familiar to *nix users.
Want to do a directory listing of all files matching a patter? Try ls *.txt. It will work in both bash and PowerShell. The arguments are different in PowerShell, but it's just a man ls to find out what they are (or just use the more convenient tab completion). Of course, those aliases are shortcuts to a verbose command naming scheme. I would think that for a very occasional user who might not remember the commands, it is far easier to use a system that has real descriptive names rather than the ultra-terse naming scheme used by *nix. Even if you can't remember the exact name in PowerShell, you can simply use a wildcard for the command name. Can't remember the command to export a CSV file? Type *csv* and keep pressing tab to cycle through the commands (or type man *csv* to see the entire list). If the occasional bash user had to export a CSV what would they do?
Also, PowerShell has a much more consistent argument naming scheme. The basic utilities on *nix have a diverse structure are arguments. For example, ls and find cover a similar subject, yet their arguments are worlds apart. You may be used to that, and so it seems familiar, but it is certainly not a simple case a sitting down and typing.
The difference is that Unix is oriented around commands and programs that take input and give output; whereas Windows is oriented around DLLs and frameworks that build on top of DLLs.
That is not an accurate assessment. PowerShell is all about commandlets and functions that take input and give output. The difference is that the input and output isn't just a stream of text, but objects. If you want to get the size of a file, you read it as a number; you don't have to convert the text in a particular position of a directory listing.
The pipeline is super-important in PowerShell. Objects, and lists of objects, are passed around and processed either sequentially or in a batch. The objects and pipeline are basically what gives PowerShell its power. To ignore that and talk about DLLs is just missing the entire point.