somewhat logical, but entirely in practice verb-noun command structure.
That’s supposed to be “impractical”, not “in practice”, for others reading along.
For example, the “proper” command to list a directory is: Get-ChildItem
The “proper” command to fetch a webpage is: Invoke-WebRequest https://example.com/
In these particular cases, they do have aliases defined, so you can use ls
, dir
and curl
instead, but …yeah, that’s still generally what the command names are like.
It’s partially more verbose than C#, which is one of the most verbose programming languages out there. I genuinely feel like this kind of defeats the point of having a scripting language in the first place, when it isn’t succinct.
Like, you’re hardly going to use it interactively, because it is so verbose, so you won’t know the commands very well. Which means, if you go to write a script with Powershell, you’ll need to look up how to do everything just as much as with a full-fledged programming language. And I do typically prefer the better tooling of a full-fledged programming language…
I also have to say, I feel like many people don’t realize how much dexterity and skill it takes to constantly crank that camera.
The twin-stick camera controls are a terrible solution, even if they may be the best we have. They are a major barrier for entry IMHO. With 2D games, you could hand a controller to someone, who doesn’t play games very much and they’d still typically be able to play along. But with 3D games, that’s so much harder, because now you have to press buttons and move the camera at the same time.
So, I imagine, even when the hardware became available, that various studios still tried to find simpler solutions.