After mulling over it for close to 14 years, it seems Microsoft is finally ready to kill off the Windows Control Panel soon. An official confirmation has been posted on its website.
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
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.
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.
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.
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.
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.
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.
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.
Great, now I’ll have to
GoogleBing for a four-line command when before I could just dig through a few menus.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
they should call it, get this, control panel
For the investor’s sake, I think it should be called the HyperPanel
Good point … unless MS manages to cripple that capability somehow.
That’s a hot take for Lemmy.
Nah, PowerShell is just a shitty bash wannabe
Actually PowerShelll is basically a wrapper for .NET classes… and it doesn’t really emulate Bash in any functional way.
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.
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.
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.
Ah, so it sucks even harder
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.
Look, if it’s not a file, I don’t want to have anything to do with it.
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.
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.
Finally linux will have parity in useability with windows.
No, it’s already more usable. You’re not bound to a GUI or hidden, indiscoverable incantations.
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.
There are PowerShell fanboys here. Anything is possible.
…and after a decade accuse Linux community for copying their great innovations.
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