this post was submitted on 23 Aug 2024
735 points (97.7% liked)

Technology

60082 readers
3523 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] partial_accumen@lemmy.world 33 points 4 months ago (3 children)

Gone in favor of ~~a less useful interface~~ Powershell commands. Fantastic!

[–] SpaceNoodle@lemmy.world 28 points 4 months ago (4 children)

Great, now I'll have to ~~Google~~ Bing for a four-line command when before I could just dig through a few menus.

[–] Beacon@fedia.io 13 points 4 months ago (2 children)

I mean, if there's still gonna be command line commands for all the features then there's no reason why a 3rd party couldn't make a gui app for them and recreate the control panels app

[–] whostosay@lemmy.world 19 points 4 months ago (1 children)

they should call it, get this, control panel

[–] xavier666@lemm.ee 2 points 4 months ago

For the investor's sake, I think it should be called the HyperPanel

[–] SpaceNoodle@lemmy.world 7 points 4 months ago

Good point ... unless MS manages to cripple that capability somehow.

[–] helenslunch@feddit.nl 3 points 4 months ago (1 children)
[–] SpaceNoodle@lemmy.world 5 points 4 months ago (2 children)

Nah, PowerShell is just a shitty bash wannabe

[–] NaibofTabr@infosec.pub 5 points 4 months ago (2 children)

Actually PowerShelll is basically a wrapper for .NET classes... and it doesn't really emulate Bash in any functional way.

[–] xavier666@lemm.ee 7 points 4 months ago (1 children)

The little time I have spent on powershell, I found it to be very slow. The input is also very verbose. I'm sure someone will say it allows one to be specific but I can be equally specific in bash as well. It's like the Java Enterprise of scripting language.

[–] NaibofTabr@infosec.pub 5 points 4 months ago* (last edited 4 months ago) (1 children)

It is verbose. It's intended to be readable by untrained people, with a consistent verb-subject format for commands (e.g. Get-ChildItem, Set-Variable), though it turns out that concept doesn't scale very well and the format gets increasingly broken when you get into the Azure PowerShell commands (New-AzLoadBalancerInboundNatRuleConfig).

The real power of PowerShell is that it can interact with .NET directly (because it is .NET), which allows you to quickly and easily build scripts for anything that uses .NET (like Windows). For instance, you can view or edit registry keys of other systems through a PowerShell remote session (using the .NET RegistryKey class), and set up a loop to edit a registry key across a list of machines remotely (I used to do this while managing on-prem AD groups in my last job, it's much faster and easier than trying to change registry keys through remote desktop sessions, more reliable because it's programmatic, and you can easily log the command output and catch any systems that failed to accept the change).

PowerShell might not be what Bash is for the average Linux user, but it's a massive improvement for managing Windows systems at scale. Anyone who works in corporate IT should learn PowerShell.

[–] xavier666@lemm.ee 2 points 4 months ago

For instance, you can view or edit registry keys of other systems through a PowerShell remote session (using the .NET RegistryKey class)

It's like a built-in Ansible equivalent (the configuring and management part at least). I'll agree that's neat. If I managed a fleet of Windows machine, I would properly learn that.

But I don't think it's something for the average home user. And the Linux way of configuring remote machines is too easy.

[–] SpaceNoodle@lemmy.world 1 points 4 months ago

Ah, so it sucks even harder

[–] Matriks404@lemmy.world 1 points 4 months ago (1 children)

Powershell has a completely different approach of working with commands than traditional Unix shells. You pretty much don't know what you are talking about.

[–] SpaceNoodle@lemmy.world 3 points 4 months ago (1 children)

Look, if it's not a file, I don't want to have anything to do with it.

[–] Matriks404@lemmy.world 0 points 4 months ago

That's fine, I also pretty much prefer standard Unix tools, due to how efficient they are, but you can't just say made up stuff with no valid explanation, because Powershell has still nothing to do with bash.

[–] Matriks404@lemmy.world 1 points 4 months ago

Powershell at first seems to be weird and clunky, but after you get used to its syntax you can quickly look up and use its commands without much guessing.

[–] Mondez@lemdro.id -1 points 4 months ago (1 children)

Finally linux will have parity in useability with windows.

[–] SpaceNoodle@lemmy.world 4 points 4 months ago* (last edited 4 months ago) (1 children)

No, it's already more usable. You're not bound to a GUI or hidden, indiscoverable incantations.

[–] Mondez@lemdro.id 1 points 4 months ago (1 children)

I felt the /s was implied but clearly enough people actually believe that linux is only for people who master arcane command lines that it could be taken as a genuine belief.

[–] SpaceNoodle@lemmy.world 0 points 4 months ago

There are PowerShell fanboys here. Anything is possible.

[–] random_character_a@lemmy.world 9 points 4 months ago

...and after a decade accuse Linux community for copying their great innovations.

[–] goferking0@lemmy.sdf.org 1 points 4 months ago

Well then it's guess which is the one to use now or which os those commands are naively installed and which need to be installed