https://goo.gl/FQl4TF

And see my “Third….”.

About the CLI, Remote Desktop is a VERY BAD way to get around having to have a CLI. Instead of saying by word what command and options to put into the command line, you have to say “Go to this menu, look for the icon that looks like a dog pissing on a policeman’s helmet… Double click on that unless you’ve set single click in the options… what? You don’t know if you have? Well, you may get two copies of the same program up, then…” and so on and so on and so on. And if they have a different version of the program, the menu items icons and hierarchy will have changed, so your instructions will merely confuse.

So they have to open up their computer COMPLETELY to some internet person to run to get the fix.

The CLI is pretty effing easy to helpdesk.

When I have to help someone with a Windows app, I know computers well enough to know roughly what I’m looking for, so it’s some hunt-and-peck for the right thing. That can only be done with complete control of their PC, though. Command line commands are fairly invariant and are entirely, necessarily, word-based. Even if there’s a lot of silly “punctuation” with “backslash dash colon” going on.

Windows tried to hide DOS and DOS was pretty minimal and pointless (Borland made their money because DOS was so worthless), and they brought that hiding into every windows OS since. They don’t troubleshoot the PC with command lines in house so they don’t see why anyone else needs it either. So they don’t get it.

Same with Windows roaming. They work like that and see no reason to do anything anyone else does if it means changing the assumptions basic to the way windows works (like sole user of the same PC every day), and when they want to change the use-case, they tack on some crud to keep the paradigm and avoid looking too deep into the code to start from a better place.

After all, changing the paradigm only gets them a lot of work to no change they can sell as an improvement.

And it sells AD to help roaming work. And when AD is being “sold” to laymen or justified by them, they go and ask “What do you do to do $THIS in Linux, eh?” when $THIS is a kludge done by Windows to allow something UNIX (therefore Linux) has been doing since the 50s in a different way that doesn’t require the hoop jumping and kludging.

But since it doesn’t have $THIS, it’s “not sufficient” and “incomplete”.

Again, it has to ape what Windows does, even if it doesn’t have to, to be accepted as a replacement for Windows.

And yes, the cli is it needed for the average desktop user in Linux no more than in windoze

So ever since 2011 or maybe 2007, depending on your distro choice.

So how is it different from Windows? You still admit you have to install the apps you use form CD.And read and agree to the license.

And most of that stuff is included on the average linux install DVD. Several programming languages, several semi-professional photo apps (including darkroom style ones like Digicam), an office suite (including full RDBMS) or two, typesetting, document converters out the wazoo, and so on. Already installed.

And most of the things not there are not there because the law makes giving them to you illegal in dumbass backward countries. Like DVD viewing software.

Which is also not included in Windows either, by the way.

More than slightly unfair.

For one, if they aped a basic app like some established player on windows, they’d be sued. See Lindows.

Second, if they aped a windows app, they’d be derided (and they are) for being a “me too”.

Third, if they don’t ape a windows app, they’re dismissed as “not standard”. See GIMP et al.

The words mean nothing to UNIX, since the design was always for roaming profiles. Only windows is STILL demanding you installed everything on the local C drive…