this post was submitted on 25 Sep 2023
436 points (83.9% liked)

Unixporn

15421 readers
1 users here now

Unixporn

Submit screenshots of all your *NIX desktops, themes, and nifty configurations, or submit anything else that will make themers happy. Maybe a server running on an Amiga, or a Thinkpad signed by Bjarne Stroustrup? Show the world how pretty your computer can be!

Rules

  1. Post On-Topic
  2. No Defaults
  3. Busy Screenshots
  4. Use High-Quality Images
  5. Include a Details Comment
  6. No NSFW
  7. No Racism or use of racist terms

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Mountaineer@aussie.zone 17 points 1 year ago (2 children)

I don't think it's strictly compliant, although they claim to have based it's syntax on Korn shell, which is the strictest definition of POSIX shells.

You can do pretty much everything in powershell that you can do in something like bash BUT, it will be done slightly differently, so trying to make a script cross compatible is pointless (you might as well just write it natively in powershell etc).

Powershell isn't inherently bad, unlike bash for instance which just allows piping out text output, Powershell can pass around true .net objects.
But if what you're looking for is cross OS compatability, you're pushing shit uphill.

99.9% of the time, I open powershell and just ssh into a "real" linux box.

[โ€“] mvirts@lemmy.world 8 points 1 year ago* (last edited 1 year ago) (1 children)

Lol except they aliased wget and curl but dont parse the standard options ๐Ÿ˜ก

[โ€“] Zeth0s@lemmy.world 6 points 1 year ago

That's borderline criminal. Nothing more to add

[โ€“] PuppyOSAndCoffee@lemmy.ml 3 points 1 year ago (1 children)

powershell is inherently bad btw

[โ€“] SeeJayEmm@lemmy.procrastinati.org 1 points 1 year ago (1 children)
[โ€“] PuppyOSAndCoffee@lemmy.ml 2 points 1 year ago (1 children)

Your quote cannot be read because reading is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.

Do your complaint is that the default security policy, that is easily changed with one command, is conservatively set?