wait a second, *censored* is this:
http://www.linuxquestions.org/questions/general-10/linux-distros-too-hard-to-use-801102/thank you so much Cityscape for taking that completely out of context and misinterpreting what I said. My post was in response to <your> post.
Anyway, yes, there are graphical tools equivalent to most of the commands used. (actually, the number of built in applications is (obviously) a lot larger then windows, (there is a reason for that, although it's rather stupid).
Also, I fail to see how using sudo with apt-get is a issue... (
)
Doesn't seem he knows too much about security risks.
The only reason I use sudo apt-get is because when you use apt-get without using sudo (or su, which I think can be used for the same purpose with certain options), it complains and helpfully asks "Are you root?"- so I used sudo. (Is there another way that is "better" to use apt-get properly from the terminal?) That's all. Of course running programs as root can be bad in cases where somebody else can control the flow of the program (consider stack overwriting code that takes advantage of the all too common flaw whereby programmers insist on using printf() with a single argument that was provided externally; that input can be manipulated so that printf overwrites the stack with user-injected code, and the RET instruction that would otherwise be issues at the end of main() (or whichever subroutine the program happens to be in) "returns" control to the injected piece of code. this injected piece of code usually just runs the shell; which is now rooted since the program was.
So the security implications only go as far as you "trust" the creators of the program.
Also, since I'm running the apt-get directly on my local machine, I could only have a security issue (from what I can tell) if the repository is compromised. I would certainly hope that that doesn't happen.
Anyway, my point was, as far as Linux has come, there are a few minor issues here and there that can be an incredible roadblock to the users migrating from windows; now, I don't mean users who are experienced with windows and know the various in's and outs of it's mechanics, but rather for people that use word every day.
Actually, come to think of it, they could probably shift to OpenOffice on, say, Ubuntu, pretty easily; and they would probably only have issues with the very same things they would have issues with on other operating systems (driver installation is "scary" to a lot of people, regardless of OS). So in that regard my post was certainly stretched into hyperbole.
I also noted that a common distribution method for Linux software is that it is only given in source; usually with a makefile and instructions. This needs amendment as well, since, as mentioned, there are a vast number of applications available through the package managers of most distributions. This would suite people just fine, however, sometimes they aren't the latest version (keeping a repository up to date is probably no easy task) in which case you would (usually) need to go to the program's sourceforge or similar page, download a tarball (or whatever they packaged it as), extract it, and run the appropriate make command.
This of course doesn't apply to the extreme beginner, who is more then happy with the out of date, but functional version, but rather to the users who have this urge to always have the latest and greatest of all of them- that is, the learning curve goes from getting, say, version 1.4 via the package manager hassle free, or having to download version 1.6 and extract and compile it themselves (and yes, the various graphical tools help in this regard, my linux time is about 50/50 outside of a graphical environment and inside it, which perhaps provides a pear-shaped view of exactly what the "average" user would experience. Anyways, it's not so much how difficult it is but more the increase in complexity from the package manager to getting versions that aren't in the repository.
Inevitably, one of the "standard" (OpenOffice convertee) will need assistance with a specific feature, and will learn that it is a bug, or an issue, or something along those lines (such as being added) in the latest version of OpenOffice; and they may find that that version is not within their package manager; so they have to climb a rather steep learning curve.