The Elements of Style: Unix as Literature
theody.net
theody.net
I discovered UNIX back in 1990. By 1991 I was working with a full-featured GUI. Around 1993 I thought I should take a look at this new-fangled 'Windows' that everybody on the Internet was raving about. I couldn't believe how horribly primitive it was. Windows didn't become usable, IMHO, until Windows 95, so by then it was a full four years at least behind the half-dozen or so UNIX desktops that were based on X11. (And even then, it wasn't a true pre-emptive multi-tasking OS.)
Windows in 2020 still hasn't caught up with the network-based X11 that can easily run a program on a machine in Britain and have it launched, controlled and displayed on a desktop in New Zealand.
Windows has RDP support, which is strictly better than X11 forwarding because it allows for seamless operation of many multimedia-oriented features that would be expected from modern desktop sessions on any OS. I remember it supporting printer, drive, sound and USB forwarding, all of which aren't possible with plain X11 without filling in the gaps yourself.
The de-facto standard solutions from third party suppliers like TeamViewer are also a significant alternative for cross-platform usage.
The thing is, they have not anticipated all my needs. Instead they have, through the GUI, limited what I can do. Inevitably this becomes a business objective, to limit what the user does, in order to further the company's interests, instead of the user's.
If mastery of UNIX (CLI) offers real freedom, then what does mastery of Windows (GUIs) offer.
Employment perhaps. In any case, something less than real freedom.
I am kidding of course.
That, and some windows-heavy projects still have a large amount of Batch files.
That being said, I'm super glad to have access to it when I'm stuck on Windows for deploys or the like.