A Continuing Work in Progress: The State of Linux 2006 - Page 2
Forum Motherboard & Memory : Memory - A Continuing Work in Progress: The State of Linux 2006
Last message on previous page:
| Quote : http://www.reallifecomics.com/archive/991213.html
|
Ain't that the truth!!!!
:-D
Where's Spud?, he HAS to say "word" to that xDxD
| Quote : "I think file-sharing for a folder being in that folder's settings menu is quite intuitive. "Is my folder being shared? Well lets look at its settings. Yup."
|
Alright, I'll bite.
The setting I'm refering to in the Folders area is the infamous "simple filesharing" setting. I would thing it would rather be in the tab where you actually share the folder. What I was refering to is the Folder Options in Control Panel. Two separate things. I agree with what you said, but it was not the argument I was making.
Windows will always try to autofind printers because, like I said, the "master" setting is in Control Panel->Folder Options. Again, two valid arguments about two separate things.
About the autoloading thing, I will conceded that yes, you can do that on an individual basis (per device and per media type) but I would really expect there to be a simple, accessible way to prevent this universally. You know, like what Gnome/KDE offers (but I will concede that Vista does exactly this)
| Quote : http://www.reallifecomics.com/archive/991213.html
|
Ain't that the truth!!!!
:-D
Where's Spud?, he HAS to say "word" to that xDxD
f'shizzle!
http://www.machall.com/index.php?strip_id=257
Another one, but not as funny as the others
| Quote : Yahoo reports and Microsoft has admitted this 8O
|
http://yro.slashdot.org/article.pl [...] hreshold=1
http://news.yahoo.com/s/ap/2006060 [...] hvBHNlYwM-
And I care--because?
This is no problem for me. I knew you would come back to defend linux, didn't realize you would do so by attacking Microsoft. As I said before, regardless of difficulty setting up Linux, in some--perhaps many--configurations, it is better suited for running mission-critical tasks. However, there are many more client computers than there are servers, and Server 2003 does a dang good job these days.
Why resort to attacking Microsoft? This is about Linux, is it not? Yes, Microsoft has its problems, and it has had huge, gigantic flaws, but Linux is a double-edged sword in that it excels due to its open-source--while it is not universal like Windows is. Incompatible software is a nightmare because saying "X driver or X software runs perfectly on Linux" depends on which of the dozen or so popular flavors of Linux we're talking about. Microsoft has different client and server OS versions, and yes, x64 vs. x86 versions now too, but of the currently supported versions, really we're talking 4 or 5 big ones. Most if not all Windows 2000 apps work on Windows XP, and heck even most Win2k drivers work with XP, so really only 3 or 4.
Again though--why mention something so off-topic? We were getting off-topic as-is, and even if you expose a weakness microsoft has that I have not known before, does that make linux any better? Oh, nevermind. I'm not a linux hater--but you certainly seem to want to create anti-linux flames--perhaps to catch us in error while flaming without reasoning...
Here I go talking about staying on-topic and lol I just brought us even MORE off topic
You should care if you have any interest in the right to privacy. M$ is constantly trying to invade our privacy.
Personally, this is just the kind of thing that puts me off windows. I like my personal privacy and know it's in safe hands with linux.
I think it basically boils down to "know-how" and "show-how". In windows all the config settings are in these big wizards, which have to make a lot of assumptions to "dumb down" the setting so that the average user has a clue what's going on. Linux doesn't have all of that luxury (for some), but it gives you absolute power over what's going on. I love Linux. Its just like everyone's said, linux's lack of support for games is just the death nail in the coffin for a widespread desktop OS. For that reason I dual boot my desktop computer.
Just a thought, is there a way to turn off that little bit of code that Micro$oft has built in to "check on" the validation every time you boot? How many lines of HEX code would you have to sift through in the registry to find it? I'm not about to try, but 2000 lines of well commented config files doesn't sound so bad after thinking about that.
Perhaps the thing I hate most about windows is it asks, "Are you sure?!" Fifty million times before 9 of 10 commands. As far as a testimate to absolute power, go delete /bin sometime (I've tried it), you wont here a peep out of linux. Never tired this, just because I'm afraid of all the "Are you sure?!?" boxes I'd get, but try deleting /windows/system32 sometime. That'll make some noise.
If you try to delete windows/system32/ it might give two "are you sures" at most. Then it will try, run into a file currently in use, give an error and stop.
Next time you try to boot you would be lucky to get a windows protection error.
Just figured I would save you the curiousity.
Personally I hate wizards. The gui however is very intuitive and easy to use. Very much unlike Linux.
Yes KDE and Gnome are easy to use and intuitive... for what they do... which isn't honestly that much.
They lack the sheer volume of options that Windows has in the GUI.
Also, as for the registry being a giant complex mess to wade through... honestly it is fairly simply laid out. It is just easy to hide things in it if you want them hidden.
I hack my registry all the time. There are several ways to track down offending entries if you know enough about them. No different really than tracking down the right configuration file and editing it.
The difference is how often you have to do it. With Windows you can utilize several of its advanced features without ever even thinking about the registry. In Linux, in order to get ANYTHING interesting done, you HAVE to hunt down config files. Therein lies my main complaint.
Also Linux needs a single standardized installer that bundles all dependancies in the installation files. That would make a HUGE difference.
As it is now, if I install an rpm file for instance, I have no clue where it put the files if they aren't in the standard places. I would have browse through the source to figure that out. Windows installers are much more informative.
| Quote : If you try to delete windows/system32/ it might give two "are you sures" at most. Then it will try, run into a file currently in use, give an error and stop.
|
If you try to do a "rm -rf /usr/lib" (analogous to /windows/system32), you will encounter exactly one error:
"Cannot delete <first file in /usr/lib>: Permission denied."
Then it dumps you back at your user CLI prompt.
| Quote : Personally I hate wizards. |
Me too. They suck.
| Quote : The gui however is very intuitive and easy to use. Very much unlike Linux. |
I assume that you've never used anything but a terminal in Linux then? KDE, Gnome, and XFCE are excellent GUIs. Windows Explorer is very, very stripped-down and klunky compared to what you can do with Konqueror, Nautilus, or Thunar.
| Quote : Yes KDE and Gnome are easy to use and intuitive... for what they do... which isn't honestly that much. |
What do you want your GUI to do? Have Clippy write that paper for you? A good GUI and a good OS are transparent- you don't notice it as its only function is to help you accomplish your work (or play.) If they are doing their job, you never should notice them.
| Quote : They lack the sheer volume of options that Windows has in the GUI. |
Like:
1. 3rd-party themes support without having to pay for Window Blinds or that ugly uxtheme.dll hack.
2. Built-in SFTP capabilities from the file browser.
3. Tabbed file browsing and multiple panes (Konqueror)
4. Previews for more than just images in the file browser window for ALL of the icons (not just the side pane)
5. The choice of different window managers and file browsers.
The list goes on. Windows has a MUCH less configurable GUI. Look at the KDE or Gnome control centers and then at the Windows "appearance" tab and tell me which one has more options.
| Quote : Also, as for the registry being a giant complex mess to wade through... honestly it is fairly simply laid out. |
So HKEY_LOCAL_USERS/{a567d390-d29b576a-58ea7b89-56782a7e}/VENDOR/APP_NAME/REG_KEY and a hex key is easier than /home/user/.app-name/conf-file where the config file is marked like:
#To enable feature, uncomment FEATURE below:
#FEATURE
Hmm. I kind of thought that it would be the other way around, but hey, if editing hex keys after hunting down a 32-digit hex identifier is easier, it's whatever floats your boat.
| Quote : It is just easy to hide things in it if you want them hidden. |
That's certainly true. But why would you want somebody to hide things on your computer? I sure as heck don't!
| Quote : I hack my registry all the time. There are several ways to track down offending entries if you know enough about them. No different really than tracking down the right configuration file and editing it. |
If you know that 32-digit hex ID code for the application and the right hex value, I suppose. Also, if you like to have to sift through 4 different temp folders, Application Data, etc. I just look in /home/user/. and I'll see every single little config file that has to do with my user account. System-wide ones are all in /etc, most in /etc/conf.d.
| Quote : The difference is how often you have to do it. With Windows you can utilize several of its advanced features without ever even thinking about the registry. |
I guess turning off Clippy must count as an advanced feature. You have to hack that damn registry to even *truly* disable autoplay on the CD-ROM drives for crying out loud.
| Quote : In Linux, in order to get ANYTHING interesting done, you HAVE to hunt down config files. Therein lies my main complaint. |
There are a lot of GUI tools in Linux too. Download SuSE 10.1 and tell me how many config files you have to edit since YaST is there. Also, I'd take config files over a huge monolithic registry any day. If the registry crashes, better hunt down your Windows install disc and all of the reg codes for your software and hope that Mother says you may reinstall them because unless you're lucky and happen to have a recent system backup handy, there's no way in God's green earth that you're going to recover. If there is a config file problem in Linux, well, shoot, you boot a live CD and edit the thing, reboot, and you have a working system within 5 minutes. I've done it. It works.
| Quote : Also Linux needs a single standardized installer that bundles all dependancies in the installation files. That would make a HUGE difference. As it is now, if I install an rpm file for instance, I have no clue where it put the files if they aren't in the standard places. I would have browse through the source to figure that out. Windows installers are much more informative. |
That is a consideration, especially if you install a lot of packaged from outside the repositories. It used to be much worse in the past- they didn't call it a "dependency hell" for nothing. But repositories have gotten MUCH larger- Debian's is now 20,000+ packages and the maintainers do a very good job of keeping all the dependencies needed by the packages in the repository all present.
Linux uses package dependencies to increase performance and provide a much easier way to patch and upgrade systems. If you have 15 packages that use a certain library, let's call it "foo," then you need only install one copy of foo and each of the programs can use it. In Windows, each one of the15 programs needs to have its own copy of foo. In the old days, having 14 less copies of foo was a large benefit, but since hard drives have gotten bigger, that is really not an issue. But it is once you realize that if you run more than one program that uses the foo library, each must load it into RAM whereas Linux need only one copy of foo to be loaded.
Today, the security angle is more important. If the package foo needs to be patched because of a security issue, you can simply replace the old foo with a new foo and all 15 programs are now fine. In Windows, you must patch all 15 programs to fix the vulnerability. I bet that not all 15 programs have very timely security updates, so you could have an unpatched hole in your system for far longer than you would in Linux.
Oh, and you can look at the "files installed" tab to see what's all in an RPM or DEB and where it goes in the system. I'd like to see that in Windows software too, but when that happens, I'll see Durocs and Landraces flying with the hawks. Sony's not exactly going to tell you that they installed rootkit.exe in C:$SYS$.
Thank you MU_Engineer, I don't know that I coulda said it better myself.
I really think this whole thing boils down to what you're used to. I agree that Windows makes many things very simple to do, but on the same page a properly configured Linux distro (like the ones that are shipping today) also make many tasks dead-simple.
Both can also make some tasks a real headache. The various regedits are a fine example, and I don't care what you say, package management systems are only as good as the individuals who set it up, and inevitably you'll either find software that's not in the system or one that fails to be installed properly with the system and you are forced torevert to manual compilation and installation. Not that doing that is incredibly difficult, but don't expect Joe Sixpack to do it.
c4onastick also makes a fine point and somewhat sums up a differnet aspect of the whole thing, Windows is about results with minimal hassle, Linux is about more impressive results with more effort. If this weren't the case, if Windows was clearly as able as Linux in some aspects, our routers, TiVos, etc. would be running Windows CE .NET,not a variation of Linux.
Like I said before, Windows has it's strengths, Linux has it's strengths, and you should use which ever has the strengths you need. If you aren't comfortable using one or the other, you can probably make the one you are comfortable with duplicate the abilities of the other, usually at some cost, if you can't/don't want to become familiar with the other.
Well you certainly are thorough.
| Quote : I assume that you've never used anything but a terminal in Linux then? KDE, Gnome, and XFCE are excellent GUIs. Windows Explorer is very, very stripped-down and klunky compared to what you can do with Konqueror, Nautilus, or Thunar. |
I have used both KDE and Gnome. They are both wonderful for navigating your directory structure and looking at files. They are significantly less capable at configuring your computer. Or at least they were last time I tried them.
One specific example is setting up NAT. In Windows you just go into network properties on your network card and click on a check box. There are more options there if you want to configure something specific.
In Linux, for a newbie, setting up IP masqing is a nightmare. Just figuring out where to look for help is not at all easy. The MAN files are generally poorly laid out, poorly written, and not very layman friendly. The SAG and NAG are a bit better but still not very good for a targeted search.
Also, setting up a parallel port zip drive in Linux was anything but a cakewalk. You could argue that this is because of Iomega not providing good driver support, but the fact remains that it took me about a full day of hair pulling.
Then you have general configuration for other things such as setting up a domain and configuring a DNS server, etc.
All of this stuff is fairly simple and straightforward in Windows. No clippy involved. Hell half the things in the Windows Control panel are missing from the Linux GUIs. Thats that stuff I am talking about. Thats the stuff that matters.
| Quote : So HKEY_LOCAL_USERS/{a567d390-d29b576a-58ea7b89-56782a7e}/VENDOR/APP_NAME/REG_KEY and a hex key is easier than /home/user/.app-name/conf-file where the config file is marked like:
|
Honestly, I have never felt the need to play with a hex editor in the registry because regedit generally does a good job of translating things when needed. Also usually when I go into the registry I am looking for things like
HKEY_LOCAL_MACHINE/software/microsoft/Windows/currentversion/
Or possibly some game or software product that is listed under the manufacturer's name.
Again, I need to visit my registry much less often than I would need to track down config files in Linux to get the same job done.
| Quote : I guess turning off Clippy must count as an advanced feature. |
Right click clippy, choose hide. He doesn't bother me anymore.
I do not claim that Microsoft is anything other than a monolithic evil empire, but so far they have produced an operating system that is complex enough to satisfy most curious techs' desire to tinker and simple enough to figure out without much effort.
Yes it has lackluster security, hidden files, and more problems than I could shake a stick at, but it works and I don't have to spend several days beating myself up to figure out the solution to a problem. Generally if I do run into a major problem I can fix it in an hour or two. In Linux, it was MUCH more frustrating.
I post these problems not as a taunt saying 'Windows is better than Linux nya nya' but in an attempt to encourage the Linux community to do something about them thus putting them into a position for increased market share and eventually allow me to replace my Windows PC with one running an operating system that is intuitive, easy to use and troubleshoot, and is free from evil DRM garbage and imperical control.
I really do want Linux to be everything that anyone would want from an operating system. I would like nothing more than to see it replace all commercial proprietary operating systems on the market. But as it is now, it fails in intuitive interface and ease of use.
I would strongly recommend that you try SuSE Linux as the control/config tool, YaST, does just about everything that you mentioned there with a very nice GUI, especially the network config. I never had to touch a single config file when I ran SuSE, and I ran it for almost 2 years- the YaST system is that powerful. It may or may not be able to help with the paraport ZIP drive- if you don't have drivers because of the manufacturer, don't blame the OS.
I bet that you didn't like the manpages as they are viewed from within a terminal window with less and that they are more documenting what the program does and not do much how to set it up and use it such as Windows' help files do. The first issue can be resolved easily. If you're in KDE, there is a very good and searchable help index, and you can view manpages nicely formatted in Konqueror by typing in "man
<topic>" into the URL bar, or type in "#<topic>" into the run dialog. The second one requires looking online a support site such as the vendor's support site or a place like LinuxQuestions.org.
Linux does take a little getting used to as it is different from Windows. And there is a little more user knowledge and interaction required to get the OS configured and running properly than with Windows. But once it is running, it takes far less upkeep and tweaking to keep running well. You actually get real updates with Linux and not just security patches, and it is not that common that you have to reboot as the system is rock-solid and updates rarely require a reboot (only kernel patches require a restart.)
There is an old adage, which I took a small liberty with:
"Linux is user-friendly; it is just picky who its friends are."
It pays to remember the origin of the two OSes. Microsoft made Windows to easy-up the formidable-looking DOS shell so that neophytes can jump right into using the OS without needing to learn much if anything. They did this by eliminating a lot of the configurability of the OS and made choices for the user. That trend was continued a lot in subsequent versions, where you can't even start in text mode anymore. The Control Panel may help new users set up some general options, but anything more advanced requires digging into the registry or maybe can't even be accomplished easily at all. (Mounting of devices immediately comes to mind.)
Linux was made to be a very fast and powerful, full-featured OS made by programmers and UNIX experts initially for programmers and UNIX experts. The UNIX guys used generally nothing but a terminal or at the very most X11 and the relatively rudimentary CDE desktop to configure their AIX, UnixWare, SunOS, IRIX, or other UNIX machine, so naturally Linux had plaintext config files too, and these files allowed the user to have complete and utter control over the system at the expense of being a little tough to decipher and get completely right at times. At a later date, some enterprising individuals saw the potential of a Linux-powered desktop and started to graft GUI frontends to the config files so that people who used MacOS, Windows, or no computer at all would be comfortable using the OS. Since the text files came first, the GUI tools had to catch up and that leads to some gaps in the GUI-only configuration ability.
However, reducing choice to make things "easier" by simply setting defaults and allowing only editing of certain functions with a GUI tool is always much easier that expanding the scope of some tool's functionality if the core functionality in the OS isn't there already. So Linux will be made more "newbie-friendly" much easier than Windows will be made to give the user more control over her system.[/i]
I do admit to having given up on Suse a long time ago when I tried to do some configurations and discovered that the configuration utilities had bizzare and often hard to guess names that I had to look up on the internet every time I wanted to do something.
If those files have been placed in a location that is intutive (ie a control panel like section of the gui) then that would help immensely.
| Quote : The Control Panel may help new users set up some general options, but anything more advanced requires digging into the registry or maybe can't even be accomplished easily at all. (Mounting of devices immediately comes to mind.) |
... again with the registry... Seriously you don't need to dig in the registry for any but the most obscure of options. If the Control panel doesn't do it then use the mmc (microsoft management console). Speaking of which that is something that would help Linux a lot. Some Linux equivalent of the mmc, a gui that can load easy to program snap ins that all function very similarly. That is where Microsoft tends to "hide" its more advanced options.
As far as mounting of devices.... I'm not sure what difficulty you would have with this in Windows. Do you mean dismounting them? Windows automounts all drives pretty well. Even removable drives are handled very easily. If you are wanting to make a fixed drive removable that was very easy in Win 9x, a bit more difficult in XP but still doable.
| Quote : However, reducing choice to make things "easier" by simply setting defaults and allowing only editing of certain functions with a GUI tool is always much easier that expanding the scope of some tool's functionality if the core functionality in the OS isn't there already. So Linux will be made more "newbie-friendly" much easier than Windows will be made to give the user more control over her system |
Good, then make it so. A lot of options will 99 times out of 100 be set the exact same way. So remove those options from the GUI and make them defaults that can only be changed through editing the config file, I'm fine with that.
I agree that Linux CAN be made to be this way. The more intuitive and user friendly it gets, the more low end home systems will be loaded with it, then the larger the install base will get, and the more programs will be written for it.
There are 8 identified and unidentified users. To see the list of identified users, Click here.
Please mind
You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.
