CougTek
Hairy Aussie
KDE 3.04 has been released earlier this month. It's available in RPM and SRPM format on kde.org. A RPM package is supposed to be "click-and-run" from what I read on the Net. Clicking on the farious .rpm I downloaded to upgrade my KDE version simply fails. When I double-click any of the many .rpm files I downloaded, I receive an error message telling me that I'm missing some files (dependency problem). How can I have dependency problems since I'm using KDE 3.03? How stupid is that?
There's no real detailed "how-to" on KDE's web site, at least none that is easily accessable (if there's a link, it's not obvious). I found this for helping me to compile the source code (haven't tried it yet), but nothing about the .rpm. If I need to copy those files in a certain directory, is it that hard to write where?
The same goes for many other programs under Linux. You follow the (often scant) installation instructions you find on the author's web site, but for some mysterious reasons, it doesn't work as advertized.
No wonder why Linux can't compete against the bloated Winblows on the desktop scene. Every damn upgrgade or installation is a pain, purely and simply. Linux developpers seem to take for granted that everyone of their users already knows all the basics of Linux' way of working. I admit I'm way better at fixing hardware issues than software thingies, but still, I have advanced computer knowledge but I can't make my damn Linux installation work properly. How can you expect to seduce the mass when guys like me can't find their way in this environment.
Other complains :
There's no real detailed "how-to" on KDE's web site, at least none that is easily accessable (if there's a link, it's not obvious). I found this for helping me to compile the source code (haven't tried it yet), but nothing about the .rpm. If I need to copy those files in a certain directory, is it that hard to write where?
The same goes for many other programs under Linux. You follow the (often scant) installation instructions you find on the author's web site, but for some mysterious reasons, it doesn't work as advertized.
No wonder why Linux can't compete against the bloated Winblows on the desktop scene. Every damn upgrgade or installation is a pain, purely and simply. Linux developpers seem to take for granted that everyone of their users already knows all the basics of Linux' way of working. I admit I'm way better at fixing hardware issues than software thingies, but still, I have advanced computer knowledge but I can't make my damn Linux installation work properly. How can you expect to seduce the mass when guys like me can't find their way in this environment.
Other complains :
- Once you told your distro that you want to start any Xfree86-based environment (Gnome or KDE), there's apparently no easy way to just quit the window manager and return to the shell. You can open a terminal, but I haven't found how to just quit KDE. This is a shame that such an option isn't included just aside the Logout button.
There is a "kill" function on Linux that you can use to terminate a (usually crashed) program. I didn't find where was that function on KDE or Gnome.
I have yet to find something similar to Winblows' task manager on Linux. A task manager listing how much memory each application uses and with a kill button would be very useful.
RPM that do work. I have yet to find ONE. That or anything else that would allow me to have a single-click executable that would install properly the program I'm trying to get on my system. The complicated instructions to install every damn applications on Linux is unforgivable. I mean, whatever the distro (or at least the main distros), the file structure is more or less the same (/, /root, /home, /usr, /var, /usr/lib, etc). What is so hard in creating a simple installation file that would simply dispatch the files where they should be? Hey, it's far more complicated on Winblows (writing lines in various Windows' core files) but everyone seems able to make one. Creating a correct installation file on Linux shouldn't be more complicated than making a dumb .bat on DOS. I'm no programmer, but I was able to do that. Why no one has done it yet on Linux is hard to understand.
Make compiling programs easier. Most distro compile programs for an i386. Some go as far as the i586 instructions. With that in mind, why don't we already have an option where we could just right-click on a source-code file and see a "re-compile with XXX compiler"? This should have been integrated into the windows environment long ago.
Stop to require Root priviledge for installing applications where they should be (/usr). This is a real pain and a time-losing step. You won't corrupt the whole kernel just by adding a directory and a few files in /usr, so why asking root login? Just protect the places where the kernel's guts are and give me a little peace about the rest. The way things currently are, this incite the users to clutter their /home directory. From what I read on Linux desired files locations, this isn't an ideal situation. Currently, on my default installation of Mandrake 9, I have to log as root to add a pluggin for netscape-like browsers in /usr/lib/netscape/pluggins. This is utterly unacceptable unless you want to scare people from using your OS.