Sort of. Mono is the open source implementation, but it never seems to be fully compatible. The real .NET 5 from Microsoft will be out for Linux some time next year.

That's really Microsofts fault, C# can easily be crossplatform, much like Java, but they insist on only developing it for Windows and Xbone.

It's pretty much exactly the same either way with Powershell. Get the objects you want, put them into the pipeline, perform operations on them.

The file paths have spaces though, and long obtuse names. That's the whole point i'm getting at. I don't even know what you are talking about.

~ represents the home directory in Powershell just like bash.

You can't use it as a path though, the only thing you can do is reference it directly "cd ~", not "cd ~\Desktop", for example cause it won't be valid. So no, not "just like bash".

Right, using explicit paths is bad form on any vaguely modern programming language.

C is from 1970s, and even back then i would say it was bad form.

No, I think you've gotten confused about the subject? You don't seem to understand what I wrote.

No you clearly don't understand what i was saying, bringing up .Net was completely for example was completely irrelevant for what i was talking about.

Especially on the server side.

Lol, if you are running a Windows server you are doing something wrong.

This would be like someone insisting that Linux doesn't have a good way to search through text files, then noting that they can't be bothered to use grep.

Still have a GUI to search files, of note it is better than Window's as it actually search contents of text files when. Though i guess it really depends on which one you are using.

That's a good thing, since it doesn't (currently) support SSH. That's coming in the next version though. The current method for remote administration on the command line is using -computer <remote system> flags. Or RDPing into the remote system.

Don't care that it doesn't support SSH, you've missed the point of that sentence.