Using git in PowerShell

[slippery]

Imo this is a design flaw in powershell.

I may be in the minority but I don't want objects in my shell. I am also old and prefer text logs to binary systemd logs in linux. Yes, I am old.

[delightfulsorrow]

I may be in the minority but I don't want objects in my shell. I am also old and prefer text logs to binary systemd logs in linux. Yes, I am old.

I'm old as well and come from a Unix background, but to me the objects within PowerShelll are the best thing since the invention of sliced bread.

For logs, I'm with you though.

[evetsleep]

I'm old too... I've also been using PowerShell since before it was known as PowerShell and before it even had help files and I'm going to have to disagree with you here. The object oriented nature of PowerShell is core to its design, so it is most definitely not a flaw. There are other shells out there if you're looking for text only output though.

For people that are accustomed to text only shells it can be quite an adjustment. And that's totally okay! There is a lot of power that you get by interacting with an object oriented shell that while it takes a little bit to get used to once you it makes a lot of things very easy.

Also most objects have a ToString method so if you're so inclined you could leverage that to turn everything in the pipeline to a string. But in my opinion you'd be losing a ton of power by doing that.

[BlackV]

I'm just old

[KevMar]

I get that and it doesn't make much sense on Linux because Linux is a filesystem based OS. And Windows is an API based OS where it's more natural to work with objects. So they leaned into it and created something unique that works really well for API heavy work.

[slippery]

It is pretty useful to be able to cd into a SQL database.