"The good news is, the school bully can steal your lunch money only once today."
Oh, well, that makes it perfectly okay, then. *eyeroll*
I don't live in a basement. But I am concerned about being held liable for what others do with my connection.
Under Windows you have Autohotkey, which I used for a number of things in the XP days such as hotkeys to change display gamma, sound volume, instantly launch a terminal etc.
A fellow AHK user here too.
Windows is ridiculously crippled for some things but it can have its own very powerful things. Another example was a freeware to minimize windows to the system tray, it could be configured so that a middle click on the minimize button does it. Under linux this will be impossible, funnily, or non trivial to do and it's certainly desktop or WM specific.
Frankly, I never had this kind of problems under Linux.
For simple reason that on Linux virtual desktops are standard feature since early days, and allow you to manage any number of applications, spread any number of desktops.
Better yet, they allowed since early days to have literally a direct keyboard shortcut to the desired application (or combination of applications): a shortcut to switch to the virtual desktop where the application is running. (For which Win-<n> is really a poor substitute.)
On Windows, you have everything packed on single screen, into a single task bar. Anything helping to manage this mess helps. But on Linux, the problems the tricks solve often have better solutions or simply non-existent.
But sure as hell, AHK on Linux would have been nice. But I mostly use it on Windows to "fix" the "broken" applications. E.g. I can play/pause VLC with a mouse click on the video, something I would definitely miss after the move to Linux. (But it is not all that bad. There are also GUI automation tools under Linux: Autokey (an attempt to reimplement the AHK on Linux), wmctrl, xdotool.)
From security perspective, the small code base is an advantage of its own.
Support for limited subset of encryption protocols is also a benefit of its own. E.g. OpenSSL still supports MD5 hashes and would happily use them if one forgets to blacklist them.
There is nothing that you can do in Bash that can't be done easier and faster in PowerShell. I guess you're just not a programmer so you don't understand it.
Man, I do Unix (and shells) for something like 15 years now. Before that 5 years Windows.
From all your words I can see that you simple failed to grasp what Unix shell is.
And yes, you can do image manipulation directly in PowerShell. It gives complete access to the entire Windows API.
Which is the whole point of the suckage of the PowerShell.
And the quirky syntax, as if they wanted to make sure that the developers would suffer just like they did with VB.
This is how I know you've never touched it. You don't even know basic information like this. Just stick with your simplistic UNIX shell, because you're obviously incapable of handling PowerShell.
I did actually handled PowerShell, though stupid security policies make it a non-starter in enterprise and limit its usefulness to developer workstations. You can't run PS1 files out of box == Universally useless.
Otherwise, I have failed to see anything new in the PowerShell beside the retarded reinvention of the "host VB".
They had a clean start - a rare and real chance to do it right - and they still have came up with that atrocity.
And even at the VB emulation, the Perl with Win32::OLE beats PowerShell handily. Because it is real programming language and the Win32::OLE gives pretty much unlimited access to every Windows capability.
I currently have a web radio transceiver front panel application that works on Linux, Windows, MacOS, Android, Amazon Kindle Fire, under Chrome, Firefox, or Opera. No porting, no software installation. See blog.algoram.com for details of what I'm writing.
The one unsupported popular platform? iOS, because Safari doesn't have the function used to acquire the microphone in the web audio API (and perhaps doesn't have other parts of that API), and Apple insists on handicapping other browsers by forcing them to use Apple's rendering engine.
I don't have any answer other than "don't buy iOS until they fix it".
Never heard of PowerShell, eh? Bash is extremely weak and lame by comparison.
LOL. Heard. Tried. Dismissed it. Definitely a tool for VB aficionados.
Anyone comparing a Unix shell to PowerShell is either illiterate or hasn't mastered the Unix shell. (Especially Bash, which not only Turing complete (aka "real programming language") but in recent version even supports the associative arrays. IMO redundant, but nice.)
Also, what does any of this have to do with the look of the GUI? Move goalposts much?
It's not the look of the user interface. It is about how the different user interfaces change what information is accessible via them.
Even your PowerShell, for example, when working with files, as retarded as that whole idea is, provides much much more meta data to crunch compared to the GUI of the (file) Explorer. But PowerShell, no matter how hard you try, can't display the thumbnails of the image files.
Well DNS isn't really secured, so if you're worried about the CIA intercepting your DNS traffic, I don't think which DNS server you use is going to be extremely important there.
But yeah, any DNS server could gather and store records about every query, and which IP address the query came from. Many people don't consider that amount of data to be invasive enough to worry about. For most people, the worst information it would leak is that, just like almost everyone else, you're visiting porn sites.
because you rarely see the OS anyway
That is true of any area of work, if you are working correctly.
Not so fast.
Under Linux, a terminal with the standard shell is immensely powerful tool.
On Windows there is simply no alternative. And if you use the huge big name tool - PhotoShop or Visual Studio - then the OS is useless to you anyway, since Windows provides only bare/no tools for the specialized tasks. And the big tools tend to eventually reimplement huge chunks of the OS inside of them, making the user often oblivious to the OS.
On Linux, you (can) have bunch of command line tools. And you can do (and automate) one hell out of literally any specialized (or generic) task using the same OS interface: the shell.
Taking DTP as an example, one of the first times I have seen Linux outside my office was a publishing agency. They had used the GIMP scripting interface from the command line to automate processing of the huge batches from the photoshoots. (PhotoShop gained the batch capabilities much much later.)
Under Windows, it might be true that seeing the OS means you are doing something wrong or inefficiently. But under Linux, the OS is a huge bonus.
You must not ever have been to Chicago.
Anyone can make an omelet with eggs. The trick is to make one with none.
