wavetrex:



How in the world can you possibly miss it ??? It's literally the 2nd thing beside the "Power" (aka, "Shutdown") button.

Are you sure you are even using Windows 10 and not Windows 7 or 8 ?? "don't know Settings exist"... that's ridiculous ! And Control Panel is well hidden in the menus after install, takes effort to find it.

I'm sure 1st-time users of a PC, with Windows 10, have NO CLUE that "Control Panel" is a thing !

Probably you are young user , i use windows since 98 , there was only control panel and for me still there is only control panel , and settings you mention is quite easy to miss as there is only small button at start menu 🙂 . Still i dont see any reason to use it , i use control panel , everything is there 🙂

kapu:

Probably you are young user

Dude, I used CP/M on Robotron PC 1715 ... to learn to program in ASM. But if you enjoy insulting people, have fun ! /me done here.

mbk1969:

True admins use command prompt! Only noobs go to Control Panel. 😎

Seeing as Windows has put so much of an effort in the past 20 years to ditch a shell prompt, any moment where you have to us one to change a setting is, IMO, bad design. Even worse when you have to deal with regedit, which I find incredibly tedious. I find myself depending on cmd a little too often (particularly for someone who doesn't use Windows often).

mbk1969:

I don`t like CMD that much, but I adore PowerShell, namely because I am .Net programmer. And Linux adepts can say whatever they want about shells, but from the programmer point of view PowerShell is a heaven.

Kinda weird for you to say that since PS is purpose-built to be more of an administrative tool whereas *nix shells are more focused on development. Perhaps the one and only thing that I like more about PS is the fact it is object-oriented, which basically obsoletes the need for awk (and that's pretty much the only CLI tool I really hate to use). I've had to use PS to manage an Exchange server, and although it wasn't difficult, I find it rather baffling how much software you have to install just to gain access. How hard could it possibly be for MS to just create a Windows variation of ssh? They already put in all the hard work of creating an entirely new scripting system, and they stopped there? If I want to manage a server, I should actually access a shell prompt of that server. Running server-side tools remotely doesn't make sense at all, and just limits your ability to perform automation.

schmidtbag:

Kinda weird for you to say that since PS is purpose-built to be more of an administrative tool whereas *nix shells are more focused on development. Perhaps the one and only thing that I like more about PS is the fact it is object-oriented, which basically obsoletes the need for awk (and that's pretty much the only CLI tool I really hate to use).

PowerShell offers script language, and whole .Net Framework library (classes). Also I can extend it by modules either in its own scripting language or in any .Net language - with simple functions, functions as commandlets, and providers for item-commandlets (there is a family of "item" commandlets - get-item, remove-item, get-itemproperties - which can work with items having a path semantic and syntax - files, registry, custom object hierarchy; at my previous company I have created a PS representation for objects from the backup/restore/partitioning domain and people were able to use it both for client`s CLI and for internal testing). So yeah, admins use it for administrative tasks, and developers use it for development. PS Also in PowerShell script I can create a .Net class (which will be compiled on the fly - with any compiler offered for .Net) and call any API functions, any C/C++ functions from C/C++ runtime binaries, any functions from any executable files at all, any COM components, any WMI components. Also it has its own IDE. So I can develop with PowerShell even without VisualStudio. PPS One of the main feature of any shell is pipeline (and redirection). All shells utilise a strings with pipelines. PowerShell utilises a .Net objects with pipeline. Unfortunately you can`t give .Net object as an input parameter for application (i.e. CreateProcess API), but if you stay in PowerShell itself you can create code which will jungle a .Net objects instead of strings. PPPS And all that was possible right from the first version of PowerShell. At start it was not rich with administrative modules, but it was rich and cool for development.