Why I left Linux for Windows. 2159

On Friday 25 August 2006 16:39, flatfish+++ stood up and addressed the mbuttes incomp.os.linux.miscas follows...:

This is not my experience, although a possible explanation for the problems you experience might be that Gnome was coded in C, while KDE was coded in C++, which has an additional layer of complexity.

Complex software can crash when the machine is performing at the edge of its abilities, e.g. through overclocking or other heat-related problems, or because of defective RAM. Your mileage may vary on this one.

I beg to differ. Setting up Windows for networking is already a kludge when you want to use it as a client, and most certainly when you intend to set up a server. The amount of security holes in Windows can never be sealed, no matter what anyone tells you.

As for DHCP, routers and whatever, this machine here is my main workstation and at the same time it is also my LAN server - it's all server-grade hardware. I get my public IP from my ISP's DHCP server - eventhough it's semi-static - and on my LAN, all machines have a static IP address. A breeze.

That goes for *every* operating system.

Then maybe you need a more up-to-date GNU-Linux distribution. Comparing Windows XP with the latest Service Packs or whatever it's called to an older GNU-Linux is comparing apples to pears - or oranges, pick your own fruit. ;-)

That is possible. Try adding...

noapic nolapic

... to theappendline for your kernel in your bootmanager's configuration file. You can try it manually at the boot prompt first if you're squeamish about altering the boot configuration.

The problem here is licensing. Commercially vended distributions may include those codecs in the package, but the freely downloadable versions may not.

You owe that to proprietary software licenses. It's not the fault of the GNU-Linux developers. Of course, if all those Windows-using GNU-Linux newbies were not so cheapskate to rather go for a freely downloadable copy than for a boxed retail pack, they wouldn't have any reason to complain,

Hardly...

First of all, the problems the previous poster addressed pertain to defects of his hardware and to the licensing of proprietary plugins. Neither has anything to do with GNU-Linux.

Secondly, this thread is not only posted tocomp.os.linux.advocacy,but to two other groups as well. As you can undoubtedly make up from my newsreader's automated introduction phrase, I'm not subscribed to comp.os.linux.advocacyanymore, but I am subscribed to one of the two other groups listed.

Thirdly, considering the amount of troll posts directed atcomp.os.linux.advocacy,-, it is no mystery why some of the GNU-Linux advocates there - okay, most of them - react with zeal whenever this kind of crap is being posted.

What you reap is what you have sown; no more, no less.

Perhaps it is true for you, but not for everyone, and certainly not in every version ofAmarok,nor in every distribution of GNU-Linux. There are too many variables to discredit one particular software package.

Again, you reap what you have sown. Had you not frantically pestered many your stalking and your recycled and cross-posted diatribes - most of which weren't even true - then you wouldn't have made so many enemies.

Note: I am not saying the above in anger or contempt. I am simply stating the obvious, regardless of what you think of me as a person. You've expressed your opinion of me - extremely incorrect as it is - far too often already, so I won't even bother refutingthatanymore. Still, it doesn't make anything of what I say any less true.

-- With kind regards,

*Aragorn* (registered GNU-Linux user #223157)