Slashdot Mirror


How Linux and Windows Stack Up in 2006

Jane Walker writes "How does Linux stack up to Windows in 2006? Experts weigh in on that question in these articles, comparing the operating systems' security, reliability and usability. Get insiders' views on Microsoft's proprietary stack versus open source software, as well as Windows-to-Linux migration tips."

193 comments

  1. Installing stuff, handling network settings by 192939495969798999 · · Score: 1

    As Linux becomes easier to install apps on and to configure for home internet usage, for regular folks it becomes more realistic to start out with it. I don't think a regular user could switch their machine from Windows to Linux with one CD and a reboot yet... right? Can anyone show us some links for how easy the switch is, and what wouldn't be supported in general after the switch?

    --
    stuff |
    1. Re:Installing stuff, handling network settings by Anonymous Coward · · Score: 0

      what wouldn't be supported in general after the switch

      In the case of Debian: Sound, video acceleration, UDMA-support (meaning harddrive-access will be dog slow), bluetooth.

      What works: vi, nethack and other useless obsolete crap.

    2. Re:Installing stuff, handling network settings by kimvette · · Score: 1, Insightful

      You haven't seen:

        - SuSE 9.1 or later
        - Mandriva (formerly Mandrake)
        - Linspire

      FWIW, it's not a single CD. It's either several CDs or a single DVD, but yes, it is doable. Boot off the DVD, follow the install wizard, you now have a dual-boot (depending on distro your NTFS partition can be resized automagically), and you have to reboot only once during the process, unlike Windows' cryptic install screens, wiping out your MBR to prevent other OSes from loading, and having to reboot 4,281 times during the install process.

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    3. Re:Installing stuff, handling network settings by Anonymous Coward · · Score: 0

      Sure: www.ubuntu.com

    4. Re:Installing stuff, handling network settings by ElleyKitten · · Score: 4, Insightful

      Linux when it works is perfect. Linux when it doesn't is just weird and fucked up. I tried installing Ubuntu for a newbie recently, and sudo decided it just wasn't going to work. So I'm futzering around with weird commands and the Ubuntu forum for a couple hours, and yeah, my newbie was real pleased with her new system. Uh huh.

      Now my home Ubuntu computer has decided (again!) that flash doesn't need sound. No more Youtube for me anymore...

      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    5. Re:Installing stuff, handling network settings by RAMMS+EIN · · Score: 3, Insightful

      ``I don't think a regular user could switch their machine from Windows to Linux with one CD and a reboot yet... right?''

      It depends on how fancy you want to get, and on your hardware. Certain distributions (e.g. Ubuntu) make it very easy to install the system while wiping everything that was there off the harddisk, and they do a good job at autodetecting a lot of hardware.

      Things get more difficult if you want to set up a dual-boot system, preserve (some) of the data that was on the harddisk before the Linux install, customize what apps are installed, run Windows or Mac software, etc. etc. Whether or not this is beyond the reach of any particular user is mostly up to how much this user knows and is willing to learn; i.e. it's not particularly difficult to wipe OpenOffice.org off an Ubuntu install and install Koffice instead, but it does take a certain amount of effort and knowledge.

      As for hardware not being supported, there are certain classes of hardware that are problematic. Most generally, any new or unpopular-with-developers hardware that doesn't adhere to some standard and for which no specification is publicly available. In particular, WinModems (software modems), wireless network cards, and video cards (specifically, the hardware acceleration features) tend to be problematic. Having said that, in each of these classes there are plenty of devices that _are_ supported, and, of course, there are devices outside these classes that don't work. Also, sometimes things fail to work in Linux because they are broken, although they happen to work in Windows; e.g. I had a laptop once whose USB controller didn't work due to a wrong value listed somewhere in the BIOS; it (sort of) worked under Windows, but it took some patches to the Linux kernel to get it to work there.

      Searching the web to see if your hardware is supported is a good idea, and I recommend anyone buying hardware to consider Linux compatibility even if they don't want to run Linux; if you ever do want to run Linux, at least your hardware won't prevent you from doing so.

      --
      Please correct me if I got my facts wrong.
    6. Re:Installing stuff, handling network settings by XeroDegrees · · Score: 1

      download this give it exec permissions and put in in /usr/bin/ then call it from the command line thus
      youtube-dl http://www.youtube.com/watch?v=whateveritis
      The youtube video is saved to the current working directory that you invoked youtube-dl from (so make sure its ~ unless you want to spend ages searching for what you downloaded) in .flv format.

    7. Re:Installing stuff, handling network settings by RobertLTux · · Score: 1

      Oh for Mandriva 2007 ive got you One better
      use the NonFree DVD One and it will
      1 hotswitch according to what arch you are on (32 or 64) after you answer a few prelim questions (where are you and what a language and WHICH 3D DESKTOP YOU WAN TO USE if any) you will get dropped onto a real Live desktop with this neat little icon labeled (install to disk). Now you will at this time be running Mandriva 2007 (with nonfree drivers if needed) so you can play around a bit then make the jump.
      So its boot from DVD and .. (there is no and)

      --
      Any person using FTFY or editing my postings agrees to a US$50.00 charge
    8. Re:Installing stuff, handling network settings by mspohr · · Score: 1
      Ubuntu Linux (and others) do install with a single CD and a reboot. My experience over about 10 recent installs is that all of my hardware (including WiFi) is supported. YMMV.

      The standard Ubuntu install comes with the usual office suite, browser, email, and many more additional apps than I've ever been able to use. If you're tied down to a particular app that only runs on Windows, then Microsoft owns your ass; otherwise, it's a piece of cake.

      --
      I don't read your sig. Why are you reading mine?
    9. Re:Installing stuff, handling network settings by Hercynium · · Score: 1

      The problem with sudo is very strange - but having sound quit on Flash is not all that uncommon.

      I've found that using either EasyUbuntu or Automatix tends to help get the multimedia stuff working. If a package update breaks it again, I just re-run which ever one I used and it fixes stuff again.

      BTW: my own experience with these two utilities, if you haven't used them yourself --

      Automatix's tweaks tend to work, but the script is often buggy and not exactly user friendly. Their repository is also almost unusably slow (frequent timeouts, leading to failed package downloads).

      EasyUbuntu is much friendlier but doesn't always finish the job, installing the multimedia packages but not always setting them up successfully.

      Automatix is constantly being updated and the community around it is active and responsive. EasyUbuntu hasn't (last I looked) had an updated release in several months and I have no clue what's going on with development.

      YMMV, When all's said and done, I personally prefer EasyUbuntu given the two choices - but it's better still to just use the tips from ubuntuguide - even though that's a PITA as well.

      No single distro works for everybody - Ubuntu's my favorite and it works on all my machines, but perhaps Mepis or Sarge or some other distro may be better for your friend. (Mepis *is* very nice)

      --
      I'm done with sigs. Sigs are lame.
    10. Re:Installing stuff, handling network settings by Eideewt · · Score: 4, Insightful

      I've had the opposite experience. Linux is great when it works. When it doesn't, it's always been broken in a sane way. I can diagnose the problem and fix a config file and be pretty confident that the problem isn't coming back. I may not have understood the problem beforehand, but after I get a handle on it the solution is obvious. Windows, on the other hand, has never made any sense when it breaks. I suspect that Windows is as rational and fixable as Linux underneath, but it's even harder to figure out the obscure tweaks that may be needed to fix it, which leaves you with solutions like "install the driver again and hope it doesn't break this time" or "try reformatting".

    11. Re:Installing stuff, handling network settings by Simon80 · · Score: 2, Informative

      I totally agree with this, most, if not all, of my experience is problems like this that can be clearly diagnosed and then fixed. Any other problems are also almost always related to hardware/drivers. In response to the original request for the "one CD switch", Ubuntu is definitely what you're looking for, you burn the one liveCD, boot off the CD into an Ubuntu that is very similar to what will be on your hard drive, and then you run the installer using a shortcut on the desktop. 6 (I think) separate pages to fill in (keyboard layout, time zone, partitioning, what to use each partition for, user name, and confirmation of the whole thing), and then it installs, asks you if you want to put grub in your Master boot record, you say yes, and you have a shiny new dual booting system. Say no, and you end up with Ubuntu on your drive but no way to boot it until you set up a bootloader to boot it up. You're asked to give you a chance to verify that the installer correctly detected the other OS on your drive.

    12. Re:Installing stuff, handling network settings by IchBinEinPenguin · · Score: 1

      To paraphrase you:
      XXX when it works is perfect. XXX when it doesn't is just weird and fucked up.
      Yeah, I agree.
      Though for me it's usually windows that's being weird, as I'm much more familiar with Linux.

    13. Re:Installing stuff, handling network settings by Dr_Banzai · · Score: 1
      From the Ubuntu Dapper wiki:
      Note: if sound doesn't work in Flash Player (for example on YouTube): sudo apt-get install alsa-oss gksudo gedit /etc/firefox/firefoxrc Change: FIREFOX_DSP="" To: FIREFOX_DSP="aoss" Restart Mozilla Firefox. Now sound should work in Flash Player.
    14. Re:Installing stuff, handling network settings by tacocat · · Score: 1

      Seems to me that it all comes down to a certain level of familiarity with the OS defines if XXX=Linux and YYY=Windows or the other way around. I think there is a fundamental difference in philosophy on how to manage an OS or how an OS should be structured to make it manageable.

      Personally I think there is a much higher level of detail available in Linux than there is in Windows. But Windows tries to be more self configurable than Linux. Proof? The configuration tool for Linux is VIM. The configuration tool for Windows is... I don't know. I haven't used Windows in almost 10 years. But from what I remember, there wasn't a configuration tool. It was uninstall/reinstall and hope for the best.

      I don't know what's best. But I know what's best for me.

    15. Re:Installing stuff, handling network settings by burdicda · · Score: 2, Funny

      I have no links but I switch on average one person a week from windows to linux
      The only panic is how they get on the internet
      A dialout modem is sheer panic....most of the time I will switch over to a known good modem
      Only once did I hit a network card that didnt work and that was a Davicom
      and then mostly the 2nd most feared thing is their printer....especially an all in one monster
      I've been lucky and never had to make an all in one work just print....or talked them into
      buying a laser printer.

      I love it when someone say's but I need to use Autocad or Photoshop and I say
      "Oh you own a legal copy do you" and 99% of the time they freak because they don't hehehehe

    16. Re:Installing stuff, handling network settings by allaryin · · Score: 1

      > having to reboot 4,281 times during the install process.

      To be fair, the last time I installed XP on a machine, the actual install itself only required 3 reboots. Patching and installing drivers after that... probably _only_ another 5 or 6 more. :P

      --
      Ammon Lauritzen http://simud.org/
    17. Re:Installing stuff, handling network settings by Cobralisk · · Score: 1
      The configuration tool for Windows is...

      Shudder... regedit. Actually there is nothing particularly evil about the tool itself. Some mechanism for comments would have been nice. The real wtf is the binary format, the "one big config file" for not only Windows, but all of your application settings as well, and the reckless abandon with which the monstrosity has grown. Single point of failure? You betcha. The actual implementation and use of the registry is a crime against nature. Somebody in Redmond should have slain this beast a decade ago. win.ini looks pretty nice by comparison.

      --
      Waiting for ad.doubleclick.net...
    18. Re:Installing stuff, handling network settings by Schraegstrichpunkt · · Score: 1
      Linux when it works is perfect. Linux when it doesn't is just weird and fucked up.

      I find it's the opposite. When Linux doesn't work, I might be able to fix it, or at least see why it's not working. With Windows, it's a black box. I can try to reboot and uninstall/reinstall various drivers, service packs, DLLs, etc., and if I'm lucky, I'll come up with a procedure that mysteriously works more often than others. Actual solutions are often nowhere to be found.

      Now my home Ubuntu computer has decided (again!) that flash doesn't need sound.

      It's probably because (proprietary) Flash doesn't support ALSA, and ALSA is how you get software mixing. It's probably trying to get exclusive access to the sound card, and failing due to something else already using the sound card.

      The simplest solution to that is to buy an SB Live! (emu10k1), or some other card that has hardware mixing support.

      In general, I find that I have way fewer problems if I just buy the hardware to suit the software I want to run, rather than the other way around. It's a bit of an expense when you first start using free Unix-like operating systems, but it saves you a ton of grief in the long run.

    19. Re:Installing stuff, handling network settings by Schraegstrichpunkt · · Score: 2, Insightful

      To be fair, the registry isn't nearly as prone to outright corruption when you're running it on NTFS 5 than it was in Win9x with FAT.

      Of course, like you say, it's such a monstrosity... you can't actually walk through it and notice a problem like you can with config files.

      The registry wasn't a bad idea (it's basically a standardized config file format with more efficient read/write and mutual exclusion), but the way Microsoft used it (HKEY_CLASSES_ROOT, anyone?) made it a mess.

    20. Re:Installing stuff, handling network settings by 1310nm · · Score: 1

      Here are the two reasons linux will never overcome Windows as a mainstream OS:

      1) Proprietary technology
      2) Copyright law

      Period.

    21. Re:Installing stuff, handling network settings by jakoz · · Score: 1

      I disagree with that... in a sense.

      Windows can be very simple to diagnose, but you have to know where to go. You have your registry. You have your error logs. You have your startup locations. That's about it.

      Anti-disclaimer: I use linux as my primary OS, and have for a long time, plus several years as a server admin. However, I have spent a long time fixing windows

      You find it easier. However, you are not the norm. At least Windows applications try somewhat to play nicely... better than much half-assed linux code. If they shit themselves, someone with relatively basic training can disgnose and fix the problem.

      I like linux because it gives me the perfect development environment. It gives me Freedom. However, being user friendly to a newb, even compared to windows, is not one of its strengths (possibly its greatest weakness). Not would I want it to be. I like things technical. I like to understand all aspects of the technical problem, so it suits me fine.

      Not so sure most windows would though. How many do you think even bothered following up on the meaning of a BSOD?

    22. Re:Installing stuff, handling network settings by ElleyKitten · · Score: 1

      Yeah, don't worry about my friend. She's back with Windows.

      As for me, I've used EasyUbuntu, Automatix, and Ubuntu Guide, and I'm just sick of tweaking stuff. I have another friend who I gave Mepis to (see my journal) and she's all cool with YouTube and podcasts and all that crap now and I'm jealous. She's the newbie, why can she do things I can't? So I think I'm going to switch to Mepis.

      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    23. Re:Installing stuff, handling network settings by ElleyKitten · · Score: 1
      From the Ubuntu Dapper wiki:
      Note: if sound doesn't work in Flash Player (for example on YouTube): sudo apt-get install alsa-oss gksudo gedit /etc/firefox/firefoxrc Change: FIREFOX_DSP="" To: FIREFOX_DSP="aoss" Restart Mozilla Firefox. Now sound should work in Flash Player.
      Whatever. I did that like 3 months ago and it didn't help. Followed some other advice in the forums, and it worked, but now it's randomly decided to stop again. Whatever. I'm switching to Mepis.
      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    24. Re:Installing stuff, handling network settings by ElleyKitten · · Score: 1
      With Windows, it's a black box. I can try to reboot and uninstall/reinstall various drivers, service packs, DLLs, etc., and if I'm lucky, I'll come up with a procedure that mysteriously works more often than others. Actual solutions are often nowhere to be found.
      I wasn't comparing it to Windows. I like Windows even less.

      It's probably because (proprietary) Flash doesn't support ALSA, and ALSA is how you get software mixing. It's probably trying to get exclusive access to the sound card, and failing due to something else already using the sound card.
      Yeah, I know, but I fixed it. I spent weeks reading forums and trying different solutions and then it worked! Now it's forgotten all of that. I don't understand why. I've been with Ubuntu since Hoary, and it seems like every release has worse sound issues. I'm sick of it.

      The simplest solution to that is to buy an SB Live! (emu10k1), or some other card that has hardware mixing support.
      Hey, that's what I've got! So how do I enable the hardware mixing?
      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    25. Re:Installing stuff, handling network settings by Phisbut · · Score: 1
      From the Ubuntu Dapper wiki:

      Note: if sound doesn't work in Flash Player (for example on YouTube): sudo apt-get install alsa-oss gksudo gedit /etc/firefox/firefoxrc Change: FIREFOX_DSP="" To: FIREFOX_DSP="aoss" Restart Mozilla Firefox. Now sound should work in Flash Player.

      If that's all it takes to have sound in Flash Player, why isn't that the default configuration? Is it again a licence thing that the default install requires broken sound?

      --
      After 3 days without programming, life becomes meaningless
      - The Tao of Programming
    26. Re:Installing stuff, handling network settings by Schraegstrichpunkt · · Score: 1
      I wasn't comparing it to Windows. I like Windows even less.

      Oh... Yeah, Linux is crap, then.

      Hey, that's what I've got! So how do I enable the hardware mixing?

      It's been a while since I had one of those cards (my brother has it now, and he lives in a different city). You shouldn't need to do anything. IIRC, the driver will simply let more than one process open the sound device at a time, rather than returning EBUSY.

    27. Re:Installing stuff, handling network settings by oc255 · · Score: 1

      Try reformatting, how true. Windows XP,2000,98, (and lesser extent 95) all seem to die slowly after 6 months of installing, uninstalling, playing with, tweaking. Performance stinks, weird bugs pop up. I see none of this elsewhere. Linux (source based distros and binary) have a 'clean' feature that kills InstallShield or uninstall. Remove Oracle on Windows, it's a 12 step unofficial process, on Solaris it's much less and you know it's gone. Windows even has that "this file might not be used anymore, want to remove it?" which isn't standardized on uninstallers. It's a huge freaking mess and it just slows to a halt in what I would consider normal usage.

      So I reinstall XP 2x a year. Gentoo takes a couple of days to compile everything but I can rip the OS back down to useless cleanly. Mac is just putting along on my old hardware, with only .plist preference files hanging around, a filling HDD and too much running at once (my own faults), but no reinstall even after a 10.3 to 10.4 upgrade.

      But my experience isn't truth.

    28. Re:Installing stuff, handling network settings by Anonymous Coward · · Score: 0

      Copyright law? Can't see where that comes into play.

      Technology has standardized, so can't really see where that comes into play either.

    29. Re:Installing stuff, handling network settings by ratboy666 · · Score: 1

      Just tongue in cheek (but this is how Windows feels for me; I can empathically understand that Linux/Unix feels this way to Windows users -- nothing works and it makes you want to throw the computer out of the window):

      <tongue>
      I have Solaris and Linux at home. Recently tried to get Windows XP going.

      Every system I install simply asks "Do you use NIS?". I say "Yes", and home directories and logins just work. Does Windows? NO IT DOESN'T. For the love of $DEITY, why doesn't the simplest possible operation work? (logging in and having my home directory)!

      Ok, I have to create users manually on Windows; I know that it is just a home install. How do I match user ids and group ids with the file server? I guess I will have to share files as "nobody" AND THEN I DISCOVER THAT NFS ISN'T INCLUDED! So much for my home directory for sure now.

      I have to install something call "Samba", and now I can see my home directory. Now, I want to run my SUN software on my fancy new LCD monitor -- well, Microsoft did include a telnet client. But, the application won't start -- can't find my GUI... That's crazy, its running -- let's try "xhost +". Nope, didn't do it. No such command. No GUI setting for it either. WAIT A MINUTE, THIS ISN'T X!

      The Windows stuff is certainly not ready for production. How much did I pay for this?!?
      </tongue>

      If a user is happy with Windows, she should stay in that world. The gap is very large. If there is a compelling reason to switch, then the switch should be driven by the user. With such a reason, installation won't be a problem.

      Just sayin'

      Ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    30. Re:Installing stuff, handling network settings by Hercynium · · Score: 1

      I read the journal entry - yep.

      *Spire are both crap. It's dissapointing 'cause I had such high hopes for their endeavor. I've tried both the free and the paid versions (got it for free during a promo) and they both made me sad. Mepis is superior on desktop and multimedia, especially in the realm of free KDE-centric distros.

      While I prefer GNOME's interface over KDE, the primary thing that keeps me with Ubuntu (over Mepis) is the size of the community, and the fact that it's been able to impress enough engineers at my place of employ that I think I may have sown the seeds necessary to start moving away from RHEL. (Many of the other engineers love debian and gentoo and *BSD and I think they're all good, but they have never appealed to the PHBs enough to get consideration)

      Happy linuxing!

      --
      I'm done with sigs. Sigs are lame.
    31. Re:Installing stuff, handling network settings by kimvette · · Score: 1

      hyperbole
      Pronunciation: hI-'p&r-b&-(")lE
      Function: noun
      Etymology: Latin, from Greek hyperbolE excess, hyperbole, hyperbola, from hyperballein to exceed, from hyper- + ballein to throw -- more at DEVIL
      : extravagant exaggeration (as "mile-high ice-cream cones")
      - hyperbolist /-list/ noun

      (HTH)

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    32. Re:Installing stuff, handling network settings by Eideewt · · Score: 2, Interesting

      I'm sure Windows is pretty easy to diagnose if you know your stuff, but I've found it much harder to get a handle on because I'm never sure what it's doing or how to make sure I've configured something as completely as possible. This is mainly because Linux is a more open system. For example, on Linux I can edit xorg.conf and be sure that I'm in control of what X is doing. If I'm trying to change my video card driver in Windows, I don't have a clue what Windows is doing underneath. The best I can do is coax it through the driver update wizard or something. Working with Windows's screwy wireless networking system is another exercise in "what the hell is really going on".

      Windows may be easier for newbs, but I don't care about that. A system that tries to do the right thing is all right but I (like you, I think) would rather just tell it the right way and know for sure that it's going to do it that way.

    33. Re:Installing stuff, handling network settings by kimvette · · Score: 1

      No, it's not prone to corruption. Just rampant growth and fragmentation. No big deal. Really. ;)

      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    34. Re:Installing stuff, handling network settings by mackyrae · · Score: 1

      I think what it is is that Flash 7 is the last one for Linux. Flash 8 files get picture and no sound. Flash 9 files get sound, but no text. At least, that's the pattern I've noticed.

      --
      look! it's a bird, it's a plane, it's....a girl? yes, a girl browsing Slashdot on Linux
  2. WTFA by Xerotope · · Score: 5, Insightful

    Where's The Fucking Article? A link to a bunch of links...great.

    1. Re:WTFA by MerlynEmrys67 · · Score: 1
      Just like Slashdot - a bunch of links to articles of various quality - with some supporting editorial text that doesn't explain the bias in the links...

      Got to love it

      --
      I have mod points and I am not afraid to use them
    2. Re:WTFA by sparkz · · Score: 1

      Welcome to Meta-Slashdot, aka "slashdot lite". Irrelevant trivia, such as the actual article, are discarded as unnecessary ;-)

      --
      Author, Shell Scripting : Expert Re
  3. Re:Well by repruhsent · · Score: 0, Insightful

    If you read the summary, you knew it wasn't impartial as soon as it mentioned "Windows to Linux migration tips."

  4. As user experience ++ so does ability to use linux by PrescriptionWarning · · Score: 1

    Anyone who has used a computer for a few years knows well enough how to navigate about a computer, even if not with a command line. Linux is getting better about being better for that average joe who wants nothing to do with a command line.

  5. The sad thing is . . . by Bluesman · · Score: 1, Interesting

    It's still much, much easier to deploy applications on Windows, even when you're using the GNU toolchain. With windows you're guaranteed binary compatibility on a majority of systems, with Linux, it's pretty much expected that your users are advanced enough to be able to compile from source.

    It's a huge pain to distribute binaries for every different distro, so unless your app becomes popular enough for other people to do that work for you, (or the distros do it themselves) then a significant amount of development time is spent just on packaging and deployment.

    Ironically, Windows with mingw et. al. seems to be a more hospitable environment toward deployment of open-source software than "Linux" is.

    --
    If moderation could change anything, it would be illegal.
    1. Re:The sad thing is . . . by mangu · · Score: 5, Insightful
      The sad thing is you don't have a clue of what you are talking about.


      Every time someone mentions blue screens, the Microsoft guys say "Oh, XP is stable for me, it never crashes!". Yet they still mention this "compile from source" which is so 1998.


      Most of the applications I use today are available in one of the Debian or Ubuntu repositories, so a simple click in synaptic or adept will install it for me, including all the necessary libraries. I have also a few other apps, such as Google Earth for instance, that aren't under the repositories, but it has been a long time since I had to compile anything.


      You Microsoft guys have no idea how complicated is getting software for Windows if you are a newbie. You just think it's easy because you are so familiar with the whole thing. Getting winamp or nero or whatever application you want is very easy if you know which app you need and where to get it. But show me where is the centralized application install function in XP, like Adept or Synaptic in Linux. Where is the simple way to look for a software to install, searching by category? I need a software to edit a video or to manage a network or to do scientific calculations, where is the simple interface where I can find it and install it with a few mouse clicks? Without knowing beforehand the name of the software? Let's face it, the closest equivalent to Synaptic or Adept in XP is Google!


      Besides, even when I had to compile stuff in the past, it was much simpler to type "./configure; make; make install" in a console than trying to solve all those "missing vbrun.dll" problems one often got when trying to install software in MS-Windows. I may be out of date myself here, because it has been a long time since I did this, but I remember that even in 1998 automake/autorun were easier to use than solving all the incompatibility problems between windows applications and DLLs.

    2. Re:The sad thing is . . . by Coryoth · · Score: 1
      It's a huge pain to distribute binaries for every different distro, so unless your app becomes popular enough for other people to do that work for you, (or the distros do it themselves) then a significant amount of development time is spent just on packaging and deployment.

      If you are writing software that isn't going to be included and packaged for you by a distribution, then you can just use Autopackage to create a single distro-agnostic binary with its own built in installer. Autopackage even provides libraries/tools to allow functionality to degrade gracefully so that, for instance, your application can use new GTK+ features if the newer library is available, but fall back to older features and still work properly if an older library is all that's available. The tools are there, all you have to do is actually use them.
    3. Re:The sad thing is . . . by turgid · · Score: 1

      With windows you're guaranteed binary compatibility on a majority of systems

      Because Windows only runs on x86 PeeCee hardware of Pentium III and later vintage. And everyone's running the same distribution (Windows XP). OK - maybe two distros, XP and 2003 Slow-Down-My-Server-To-A-Crawl Edition(TM).

      /me ducks.

    4. Re:The sad thing is . . . by RAMMS+EIN · · Score: 3, Insightful

      ``It's still much, much easier to deploy applications on Windows, even when you're using the GNU toolchain.''

      For you or for users? Installing and maintaining software that is packaged for distributions can be easier than it is on Windows, and so much software has been packaged for Debian and Ubuntu that I feel the claim that "software installation and maintenance is easier on Debian than on Windows (or OS X)" is justified. On the other hand, packaging software for various distros can put an enormous burden on the developers.

      Going the other way, providing software that can be installed on many different Linux distributions is a piece of cake for the developer. As long as you stick to a few sensible conventions (like not assuming things that tend not to be true across distros), users should be able to install your program without too much trouble, once they have all the necessary dependencies in place. Of course, this effort might still be too much for would-be users.

      Other alternatives are targetting only a select few distributions (see also my other post about "the Linux OS" not existing), and/or leaving the packaging in the hands of the distributors - arguably, it is their job. Also, it's not uncommon for users to post step by step instructions or even creating binary packages for installing software on distributions that don't include that software.

      ``With windows you're guaranteed binary compatibility on a majority of systems''

      Yes, but this comes with a hefty price tag. For example, binary compatibility will be broken the moment another hardware architecture comes along (AMD64, anyone?). It's entirely possible that this has kept PCs from evolving past x86 for so long - with actual drawbacks; various other architectures have been more performant, more affordable, etc. at various points in time. And that's just the hardware side; I'm sure many people can point out bugs and vulnerabilities that have persisted because of the need to maintain binary compatibility with some flawed earlier system.

      Also, binary compatibility isn't completely achieved on Windows, either. Think of DLL Hell, for example.

      ``with Linux, it's pretty much expected that your users are advanced enough to be able to compile from source.''

      Which doesn't have to be very advanced at all. For a lot of software, a single command suffices; often, it's the familiar ./configure && make && sudo make install mantra (which isn't necessarily more complex than your average Windows installer), and there are often front ends to the compilation that ease the process.

      Also, if a user wants to run your software on an operating system that you do not support, is it your fault or theirs if the installation isn't easy? With the source, at least they _can_ make it work.

      ``Ironically, Windows with mingw et. al. seems to be a more hospitable environment toward deployment of open-source software than "Linux" is.''

      Some companies (at least Google) actually develop their software against winelib, and then create a Windows binary that works on Windows and any x86 Linux distro with Wine installed. Although I dread the ugliness of win32 programs on Linux, it does solve the binary compatibility problem.

      --
      Please correct me if I got my facts wrong.
    5. Re:The sad thing is . . . by plague3106 · · Score: 1

      For you or for users? Installing and maintaining software that is packaged for distributions can be easier than it is on Windows, and so much software has been packaged for Debian and Ubuntu that I feel the claim that "software installation and maintenance is easier on Debian than on Windows (or OS X)" is justified. On the other hand, packaging software for various distros can put an enormous burden on the developers.

      Installing my application is simple. The users click a link and allow the installer to run. Deploying updates is even easier; it happens whenever they run the application.

      Going the other way, providing software that can be installed on many different Linux distributions is a piece of cake for the developer. As long as you stick to a few sensible conventions (like not assuming things that tend not to be true across distros), users should be able to install your program without too much trouble, once they have all the necessary dependencies in place. Of course, this effort might still be too much for would-be users.

      I don't have to limit myself in any way; as long as Windows and .Net is installed (which is being done via Windows update, and anything newer than Win2k3 includes it), my application will install and work just fine. no extra effort for me or my users.

      Yes, but this comes with a hefty price tag. For example, binary compatibility will be broken the moment another hardware architecture comes along (AMD64, anyone?). It's entirely possible that this has kept PCs from evolving past x86 for so long - with actual drawbacks; various other architectures have been more performant, more affordable, etc. at various points in time. And that's just the hardware side; I'm sure many people can point out bugs and vulnerabilities that have persisted because of the need to maintain binary compatibility with some flawed earlier system.

      Yup, just like how it was broken moving from 16 bit to 32. Opps, Windows provided backward compatability so this didn't happen. My application in particular will also run just fine on 64 bit, without any effort on my part.

      Also, binary compatibility isn't completely achieved on Windows, either. Think of DLL Hell, for example.

      This problem is going away as .Net picks up more and more steam.

      Which doesn't have to be very advanced at all. For a lot of software, a single command suffices; often, it's the familiar ./configure && make && sudo make install mantra (which isn't necessarily more complex than your average Windows installer), and there are often front ends to the compilation that ease the process.

      Yeah, that's what a user wants to do. Open a command prompt and type THAT. Very friendly. Not to mention that this method doesn't always work. I had quite a few problems compiling from source and I'm an advanced user.

      Also, if a user wants to run your software on an operating system that you do not support, is it your fault or theirs if the installation isn't easy? With the source, at least they _can_ make it work.

      Developers may make it work. A normal user will just download a program that actually does.

    6. Re:The sad thing is . . . by manno · · Score: 2, Interesting

      "You Microsoft guys have no idea how complicated is getting software for Windows if you are a newbie. You just think it's easy because you are so familiar with the whole thing. Getting winamp or nero or whatever application you want is very easy if you know which app you need and where to get it. But show me where is the centralized application install function in XP, like Adept or Synaptic in Linux."

      And where's the central repository of knowledge that tells me what's the best text editor of the 9,000 available for Linux? The best media player, the best burning software? How do I know how stable they are? Will they have the functions I need? These aren't hits against Linux at all, but it's a lot easier for me to ask the guy next to me what he uses to burn CD's rather than look it up online. And while Linux continues to hold a very small part of the market, Finding what apps to use in Windows will be an easier thing.

      Installing in Windows just as easy as installing something on Linux. Frequently it's a heck of a lot easier to set up due to gui set up, rather than having to use config files.

      I've used Ubuntu, and tried to get it up and running on various computers with various levels of success. Even with its package manager I had to trudge through the forums to find out what program does what. Not to mention the fact that in order to replace my Windows setup I need to add repositories that aren't in there by default. I know why there no there to begin with, but it's a pain to add them for every install, and every tutorial I've seen just uses the command line anyway. I know you see it as easier, but I personally don't. I've had plenty of times where I install software with the package manager, and it either doesn't install right, or completely. Resulting in an hour + spent finding out what went wrong. How to fix it, ect.

      I love the idea of open source software. I use FireFox, OO.o, InkScape, OpenVPN, VNC, all terrific programs, but using Linux as a desktop OS just is not there yet. I've been following it for only 5 years now, and I admit it's come a LONG way in just 5 short years, and I honestly believe that sooner rather than later Linux will become my OS of choice, for myself, and the friends, and family I help pro-bono. But as it stands right now it still has a very critical last 10%-15% to go.

      I wish it could have been rip-roaring to go in time for Vista, but it looks like that won't be the case... I'm looking at Vista as a large black cloud looming menacingly off in the distance. I wish Linux, was there to replace XP as my OS of choice.

    7. Re:The sad thing is . . . by RAMMS+EIN · · Score: 3, Funny

      ``Let's face it, the closest equivalent to Synaptic or Adept in XP is Google!''

      Which, of course, runs Linux.

      --
      Please correct me if I got my facts wrong.
    8. Re:The sad thing is . . . by gfxguy · · Score: 1

      I dual boot, FC5 at home, 4 at work. I didn't install 4 (one of the tech guys at work did it for me), but I did install at home, and it was a piece of cake. I've discovered now (past few months) that I'm using Linux for just about everything. I've gone back and forth over the years, but now it really is at a point, for me anyway, where it succeeds admirably on the desktop.

      I've said it before in these discussions, and I'll say it again (because repeating yourself is a sign of stupidity), the problem that most Windows users have with Linux is that it's not Windows. Full up with a GUI it looks a little like Windows, but not exactly. It doesn't function exactly the same. OO is not MS Office, even though it's got the components that the vast majority of people want (word processor and spreadsheet).

      The problem is that most people don't like change.

      As far as the problem of which text editor to use, most users don't use text editors (see, you're thinking like a programmer again). The best media player? Install them all! Just like you end up doing on Windows where you need QT, RM, Flash, WMP, etc. Burning software? Install them all and pick which one you like the best.

      The second problem is that while I believe Linux is better, for most people it simply doesn't matter. If the computer does what you want it to do, why bother switching? What compelling reason are you going to give a Windows user to switch? For that matter, what compelling reason could you give a Linux user to switch to Windows? Nothing!

      --
      Stupid sexy Flanders.
    9. Re:The sad thing is . . . by Jussi+K.+Kojootti · · Score: 1
      every tutorial I've seen just uses the command line anyway. I know you see it as easier, but I personally don't.
      I think you've misunderstood. It's actually not that people want to force CLI on you or even that they think it's easier... Giving clear, unambiguous and succinct instructions for a GUI is often impossible and almost always significantly more laborous than giving the same advice for CLI. Try it and you'll see.

      Installing in Windows just as easy as installing something on Linux. Frequently it's a heck of a lot easier to set up due to gui set up, rather than having to use config files.
      I guess these are matters of opinion... Personally I'm never going to administer a machine without proper package management again -- my memories of installing Windows and installing software on Windows are definitely not as rosy as yours. Of course it is possible that I just wasn't knowledgeable enough about administering Windows, and thus made unnecessary mistakes.
    10. Re:The sad thing is . . . by ElleyKitten · · Score: 2, Informative
      And where's the central repository of knowledge that tells me what's the best text editor of the 9,000 available for Linux? The best media player, the best burning software?
      Look, I know you're used to Windows which comes with a bare-bones text editor, a bloated pos for a media player, and no dedicated burning software, but Linux distros tend to come with decent programs to do all those things. If you're willing to use whatever some random guy uses too, then why not just stick with the perfectly usable defaults?

      Installing in Windows just as easy as installing something on Linux. Frequently it's a heck of a lot easier to set up due to gui set up, rather than having to use config files.
      Config files? No, on Ubuntu it's just point and click. Ok, type in something to search, but on the whole, less clicks than Windows installers.

      Even with its package manager I had to trudge through the forums to find out what program does what.
      It says what it does right in the description. What more information did you need?

      Not to mention the fact that in order to replace my Windows setup I need to add repositories that aren't in there by default. I know why there no there to begin with, but it's a pain to add them for every install, and every tutorial I've seen just uses the command line anyway.
      You don't have to use the command line, people just like it because it's more straight-foward. You can add them through Synaptic (forget where, not in front of my ubuntu box, sorry) or you can get EasyUbuntu, which will install mp3, flash, etc, as well. Or you could get Mepis.

      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    11. Re:The sad thing is . . . by Bluesman · · Score: 1

      I'm not talking about installation as a user. I'm talking about the time it takes to set up the software for distribution as a DEVELOPER.

      With windows, I can distribute an app as a zip file, confident it will run without adjustment on a majority of windows systems. The .dlls can be included in the directory of the app. It's five minutes of development time to create the binary, zip it up with .dlls, and ship it off to other people who'd want to use it. Or I can use NSIS as I get more advanced.

      The thing is, I have a limited amount of time as a developer of open-source software. I can afford to package for *maybe* three systems. So there's windows which is a piece of cake, FreeBSD which is a piece of cake, and then we come to Linux. . .let's pick a distro, learn its package management system, ok, we're out of valuable time I'd rather spend developing.

      This isn't a technological problem, it's an organizational one. Yet another package manager won't help.

      --
      If moderation could change anything, it would be illegal.
    12. Re:The sad thing is . . . by Bluesman · · Score: 1

      Oh, most definitely for *users* both systems are pretty much equivalent, once everything is packaged.

      I'm talking about for me, the developer, deploying for all the distros under the Linux umbrella is much more difficult than it is to deploy on Windows or FreeBSD.

      It's funny that whenever anyone brings this up, they get attacked, but really what developers want to concentrate on is writing code that's interesting to them. I can do that on any platform. I do that on Windows now because it's just so easy to share stuff. My source code is almost always portable to Linux with few or no changes, but I can't be bothered spending the few days learning each package management system for every distro. I'll expect that Linux users just compile my source.

      This means, that for every beginner out there who doesn't know how to compile from source, there's going to be a large class of applications unavailable to him when using Linux, simply because there's no standard method for deploying an app that will work with most distros.

      --
      If moderation could change anything, it would be illegal.
    13. Re:The sad thing is . . . by Jussi+K.+Kojootti · · Score: 1
      Deploying updates is even easier; it happens whenever they run the application.
      Again, easier for you... For the user this approach means tens or hundreds of applications that have their own update methods (some need to be started, some want you to click 'update' somewhere, etc.) with different UIs for the updating. It also means security implications as the user now has X additional programs that are connected to the internet.

      Stand-alone installers have some good properties compared to package management. update deployment is not one of them.

    14. Re:The sad thing is . . . by Bluesman · · Score: 1

      Thanks, I'll check into that.

      The problem from my perspective, however, is that not only do people who want to use my stuff now have to download it, but also autopackage.

      I'd love for that to become a standard, but it's not. It's a shame.

      What would be REALLY cool is an app that produced a distro specific package based on source. I think that's the kind of thing that would really help Linux as a distribution platform.

      --
      If moderation could change anything, it would be illegal.
    15. Re:The sad thing is . . . by swillden · · Score: 1

      And where's the central repository of knowledge that tells me what's the best text editor of the 9,000 available for Linux?

      Who cares? Why do you need the best, rather than just one that does the job? And who defines "best", anyway?

      Just read the descriptions, pick one that sounds like it might work for you, install it, and see if it does the job. If so, great. If not, pick another. Of course, if you have someone around that already understands the pros and cons, ask, but all of the packages in the repository do pretty much what they say they do, so in a pinch that's all the information you need.

      And how is this worse than Windows, anyway? On Windows, you still have the issue that there are multiple options available, and you still have to figure out which one you want. Except that on Windows the apps are harder to find, harder to get (perhaps costing $$) and harder to install/remove.

      Installing in Windows just as easy as installing something on Linux. Frequently it's a heck of a lot easier to set up due to gui set up, rather than having to use config files.

      Bah. Debian/Ubuntu prompt you for the key configuration information during the installation process, so you rarely have to do anything to get the app running. Not only that, most desktop apps these days do have GUI-based configuration tools.

      Even with its package manager I had to trudge through the forums to find out what program does what

      Why? They have descriptions. If you install them, they have documentation, plus you can always just try them out. Now, perhaps you *prefer* to ask, but that's different from *having* to ask.

      but using Linux as a desktop OS just is not there yet

      Damn. I guess I'm going to have to tell my wife and kids they can't use Linux any more, they're going to have to learn XP/Vista. They'll be annoyed, but they'll get over it, I'm sure.

      Of course, I'm being facetious. Obviously, Linux isn't right for everyone's desktop, especially for people who know Windows and don't enjoy learning a new platform (which is a *lot* of people). But for those who are willing to invest a little time, Linux has been an adequate desktop platform for some time, and Ubuntu is an excellent platform now. Windows is better in some ways, Ubuntu is better in others. There's not really a clear-cut winner, which is the best possible outcome for users, because competition ultimately benefits the consumer.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    16. Re:The sad thing is . . . by RAMMS+EIN · · Score: 1
      ``Installing my application is simple. The users click a link and allow the installer to run.''

      Good! Does the installer ask any questions? If so, does it explain what the questions mean, what the consequences of each answer are, and what answer one should pick?

      ``Deploying updates is even easier; it happens whenever they run the application.''

      Ooh, spyware! Or, at least, it could be...if it's closed source and it connects to your website, without me telling it to, how do I know it's only checking for updates?

      ``I don't have to limit myself in any way; as long as Windows and .Net is installed''

      Yesteryear, the same was being said about Java. The same has been said about DirectX, Internet Explorer 5.5, Winsock, etc. What it really means is that you're targetting what happens to be the Latest and Greatest (C)(R)(TM) API from Microsoft, which they will have to support in length of ages to retain binary compatibility. What will happen when Vista is released, with more Latest and Greatest APIs? Will all of these be provided on older Windows versions, too?

      ``Yup, just like how it was broken moving from 16 bit to 32. Opps, Windows provided backward compatability so this didn't happen.''

      But does Windows on Alpha or PowerPC provide binary compatibility with x86? The ability to run win16 apps on win32 uses a compatibility layer baked into the hardware, as well.

      ``My application in particular will also run just fine on 64 bit, without any effort on my part.''

      Right, because you're compiling to virtual machine code. The same trick works on any other operating system, of course.

      ``
      Also, binary compatibility isn't completely achieved on Windows, either. Think of DLL Hell, for example.


      This problem is going away as .Net picks up more and more steam.''

      At least, we can hope so.

      ``[./configure && make && make install]

      Yeah, that's what a user wants to do. Open a command prompt and type THAT.''

      I guess not. That must be why a lot of software for Linux (if it's not included in popular distros) is shipped in a single (click and run, depending on your distro) binary, much like the installers Windows software uses. Takes some effort from the developer, sure, but I don't think Windows installers come out of thin air either (but I couldn't know, I've never developed for Windows).

      ``Very friendly. Not to mention that this method doesn't always work. I had quite a few problems compiling from source and I'm an advanced user.''

      You're not alone, and this is a real problem, and it probably won't be going away. Getting compilation to Just Work across a wide variety of platforms isn't easy. Since getting binaries to Just Work depends on getting that, it's even worse. I'm just saying: keep in mind that comparing a single version of Windows on a single machine architecture to a multitude of Linux distros on a multitude of machine architectures is comparing apples and oranges.

      ``
      Also, if a user wants to run your software on an operating system that you do not support, is it your fault or theirs if the installation isn't easy? With the source, at least they _can_ make it work.


      Developers may make it work. A normal user will just download a program that actually does.'' ... and that's what many (millions?) of Ubuntu users do all the time. But if I insist on running, say, Puppy Linux, I will have to accept I don't get 15000 packages built and tested for me.
      --
      Please correct me if I got my facts wrong.
    17. Re:The sad thing is . . . by ratboy666 · · Score: 1

      Link it statically. If you don't want to do that, then include all shared objects with the application. Dynamically link with those objects from the top application directory, or ./lib.

      Rely ONLY on Clib (Xlib, and OGL). (and CLib can be supplied with the app as well).

      Voila. "Click and run" application. Include a png icon for the application as well.

      If you follow these rules, your application will be very portable. Even running with emulators such as QEMU to target SPARCs, etc.

      Now, build your application tree into a shell archive. Double click to install, double click to run.

      How is this different from the Windows approach?

      YMMV, but I don't see how
      Ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    18. Re:The sad thing is . . . by goarilla · · Score: 2, Interesting

      i dont want to sound like an asshole or something but
      ./configure; make; make install is not the way to go
      if configure fails it'll still try to make it ... etc
      ./configure && make && make install is better assuming you are root when you compile things
      (and offcorse want the program to end in the your PATH)
      best thing tho is to first read README INSTALL and then ./configure and output the options to a file
      So you can consult them first before making the thing

      ./configure && make && make install are fine for most packages but for importants programs like mplayer,mencoder you should
      take all of your time you have to compile xvid, h..., Nvidia XvMC support, .... therefore first consult the configure options and read the documentation and for
      a lot of people doing all that is just hardcore!
      when my friends see me compile mplayer altho i have frontends of mplayers installed on their pc's
      and they use it daily they say damn you're a geek and damn GNU/linux is hard but then i always
      remind them of the fact that some guy did even more hardcore shit than i did to get to compile those win
      binaries that they are all using :D

      and then they all shut up

    19. Re:The sad thing is . . . by supermank17 · · Score: 1

      Actually I'm not sure you know what you're talking about. In my house I currently have 1 Windows PC, 1 Mac laptop, and 3 Linux PCs. And he's right, its far harder to install Linux software than PC software (the mac is easiest of all, but thats a separate issue). I'll admit, apt-get and YUM have made life a lot easier. If the app is in the repository, you're good to go, you just click on the file in your package manager, and it installs. But when its not? Then you have to deal with the mess of various repositories, source code compilation, and missing dependencies. And unfortunately, I've had lots of applications I want that are missing from the repositories. And don't even get me started on trying to install browser plugins or getting multimedia to work.

      Now I know a lot of these problems aren't necessarily Linux's fault, but they do exist. And as for where to get Windows software, thats easy. You buy it from a store :-P.

    20. Re:The sad thing is . . . by RAMMS+EIN · · Score: 1

      ``I'm talking about for me, the developer, deploying for all the distros under the Linux umbrella is much more difficult than it is to deploy on Windows or FreeBSD.''

      Yes. And that's exactly because there are all these "distros under the Linux umbrella". I feel people need to realize that these are really different operating systems, otherwise we keep getting stuck in things like "Linux doesn't have $nice_property, because I know this one distro that doesn't have it". I feel, but this _is_ my personal opinion, of course, that it's much more meaningful to look at a single distro and say things like "software installation works great on Ubuntu, but it's a pity no C compiler is installed by default, because it's often needed".

      ``My source code is almost always portable to Linux with few or no changes, but I can't be bothered spending the few days learning each package management system for every distro.''

      I think expecting developers to do so is unreasonable. I made OpenBSD, Debian, and pkgsrc packages of my software for a while, but eventually I figured I was spending more time on creating the packages than on the software proper. Now, I figure my job ends with making it easy to compile the software and do staged installs, and leave the packaging up to whomever uses the packaging system.

      ``This means, that for every beginner out there who doesn't know how to compile from source, there's going to be a large class of applications unavailable to him when using Linux, simply because there's no standard method for deploying an app that will work with most distros.''

      That's assuming nobody is creating binary packages for the distro said beginner is using. This is definitely a valid assumption when your software or their distro is new and relatively unknown, and thus creates a barrier to adoption. However, this barrier will disappear over time as people package your software for more and more distros. You could kickstart the process by providing binary packages for one platform, which shouldn't take too much effort.

      --
      Please correct me if I got my facts wrong.
    21. Re:The sad thing is . . . by lowe0 · · Score: 1

      It's called CompUSA.

      There isn't a centralized repository for commercial software because no one's come up with a good business model for it yet. It's just a drawback of commercial software.

    22. Re:The sad thing is . . . by IflyRC · · Score: 1

      *IF* Microsoft created a list of software in Windows, categorized by type it would be HUGE. There is no way they could include a list of all of the software made for Windows.

      Now, for the sake of argument lets say the do include such a list that is somewhat manageable. Manageable meaning that it's not every piece of software made. Most software for Windows is not open source, therefore they would need to integrate some software purchase scenario within Windows to connect to the software maker, download the software and handle payment.

      Whats wrong with this? All of a sudden retail starts screaming because they just got cut out of the deal. CompUSA, Circuit City, Best Buy, Wal-Mart, Office Depot, Office Max, Staples, Mom & Pop's software shop in who knows where USA.
      The OTHER problem is this...who decides what goes in the list? What kind of deals get brokered? All of a sudden Microsoft is now controlling WHO I buy my software from? How about the little guy...Small Time Software Company Inc.? Does he then sue to get placed on the list? Can he legally?

      This just opens up WAY too many cans of worms. Sorry, let walk into a store and buy what I want or let me do my own research and buy online for download. Don't give me a list of what XXX Company has made deals with.

    23. Re:The sad thing is . . . by tapehands · · Score: 1

      Agreed. Last time I had to manually install software was when I decided that the stock Orinoco drivers in the kernel weren't a good choice since I needed monitor mode. I compiled the new drivers, set the modules to load, and had monitor mode at my next reboot. Since I'm using Gentoo, I do have to recompile my kernel whenever I compulsively emerge a new kernel update, but other distros handle these updates in packages...automatically configuring everything for the end user.

      Granted, not all of your hardware is going to be loved by Linux, and you may have to hassle with it to get it to work, but honestly...is the ignoramus that buys a $300 eMachine and can't install Winamp on a Windows box going to care if his nVidia card (without having the Linux binaries installed) can't get 3,000 fps out of glxgears?

      Now for a slight tangent..

      The biggest concern with that person would be browsing websites, creating documents, burning cds, downloading music, and being social online. The first major concern (browsing websites) is hampered by not all websites supporting browsers other than IE (not really the fault of Linux), and also by there being no version of Flash 8 for Linux (still not really the fault of Linux...but it seems worse than a website just not being compatible). The second concern is downloading music - I'm just overly paranoid about this, but I don't think the average Joe would be too comfortable with most of the Linux p2p offerings...and, for the legit people, I'm also not sure about the status of DRM'd services in Linux. The final concern is being social - I love and use gaim, but damnit all. Why can't I transfer files as easily as I can in the Windows version of AIM? Why can't I have easy webcam chats?

    24. Re:The sad thing is . . . by Bazouel · · Score: 1

      One out of MANY counterexamples to your argument: http://www.download.com. Come on, how many applications do you think exist on Windows ?? Do you realistically think it would be possible to have ONE central directory of all of them ? Talking about not having a clue ...

      --
      Intelligence shared is intelligence squared.
    25. Re:The sad thing is . . . by DragonWriter · · Score: 1
      And where's the central repository of knowledge that tells me what's the best text editor of the 9,000 available for Linux?


      There isn't a "best text editor" for Linux. Which text editor is best is a function of your personal tastes, the specific uses you have for it, and other things. Same, really, as on Windows (though the options are different.) No "central repository of knowledge" exists for either, you've got to figure out what works for you. There's lots of good resources on the net to find out about text editors for either platform, but without trying some out, you won't answer that question.

      Same for media players, burning software, etc.

      These aren't hits against Linux at all, but it's a lot easier for me to ask the guy next to me what he uses to burn CD's rather than look it up online.


      I thought you wanted a centralized database with feature comparisons to let you know the best of each of these applications? Now you just want some random guy that you can ask what they use? There's plenty of those for almost any kind of Linux application...

      Installing in Windows just as easy as installing something on Linux. Frequently it's a heck of a lot easier to set up due to gui set up, rather than having to use config files.


      I don't see a lot of big differences, here. Most of the stuff I install on linux either has an installer or can be installed with apt-get (or any of the GUI front-ends for that), occasionally you'll still run into stuff with a laborious manual install process, but usually that's for fairly specialized open-source projects that usually don't have binary installers for Windows, if they are even available there, so its not really a disadvantage to linux, but to particular applications.

      Now, that being said, I don't see linux replacing or threatening Windows unless someone comes up with a revolutionary distro that really redefines the user experience and forces Windows to play catch-up in an area where lots of less-technical users instantly and intuitively grasps the advantage, even if does catch up so that there isn't any more serious debate about Linux being "ready" for the average desktop user.
    26. Re: The sad thing is . . . by Dolda2000 · · Score: 1

      Amen to that. I just wanted to add to this a mention of Autopackage, which has done wonders, not only for amazing ease of installation (did you say "a few clicks"? Autopackage is one-click), but also for wide-spread binary compatibility under GNU/Linux. GNU/Linux certainly is capable of binary compatibility, it's just that most distros don't care anyway (why should they when there's APT/Yum/Portage/whathaveyou?). The Autopackage project has developed some rather sophisticated wrapper scripts around the GNU toolchain to build binaries that link to ABIs that are available on as wide a range of distros as possible.

    27. Re:The sad thing is . . . by Anonymous Coward · · Score: 0
      There isn't a "best text editor" for Linux.
      Wrong, there's emacs. *ducks*
    28. Re:The sad thing is . . . by man_of_mr_e · · Score: 1

      What if you're not using Ubuntu or Debian? Or, what if you are, but need different default options?

      for as "rare" as it is, I seem to keep running into software that's not in my distro (very common) (SUSE 10). Stuff like Analog, postfix.admin, etc... and invariably, when i go to install these apps by tarball, they require that the programs that I do have in my repository be configured in a different way than SUSE configures them.

      bah.

    29. Re:The sad thing is . . . by Anonymous Coward · · Score: 0

      He's an MS developer. He probably doesn't know what 'link it statically' means, let alone what 'linking' is. Heck, more than half the visual-foo++ programmers I've met barely know what 'compile' means, and certainly can't explain it.

    30. Re:The sad thing is . . . by Tharkban · · Score: 1

      yet another reason I like the open source approach.

      --
      Tharkban (It is a signature after all)
    31. Re:The sad thing is . . . by zerus · · Score: 1

      I got my fiance stuck on linux after making her laptop run with kde on gentoo using the xcomposite module to make it look pretty (that and she thinks the penguin is cute). I've tried to explain to her why I have to compile everything, but she still says "Isn't it easier to just make one file that will run on all of them?" As much as I hate to say it, she's right, which is why windows has the advantage. As the variations on hardware are seemingly infinite, the possibility of compatibility is much larger when the executables aren't optimized for each individual platform, but rather run in a compatibility mode (rather -mcpu=i386). While it may not seem too hard to compile our systems, the average person doesn't want to. Instead, they just want it to work with minimal effort. So I figure that every normal user needs a personal tech support person to set up and support their linux box if it's going to take off the way most linux zealots think it should.

    32. Re:The sad thing is . . . by loqi · · Score: 1

      Yup, just like how it was broken moving from 16 bit to 32. Opps, Windows provided backward compatability so this didn't happen.

      That's because the 286 -> 386 change was within the same architecture. Parent is talking about nontrivial architecture changes (such as from x86 to PPC or the like).

      My application in particular will also run just fine on 64 bit, without any effort on my part.

      Erm... "on 64-bit?" Meaning, your 32-bit application runs on a 64-bit chip with 32-bit emulation/native support? Gee gosh!

      --
      If other reasons we do lack, we swear no one will die when we attack
    33. Re:The sad thing is . . . by Anonymous Coward · · Score: 0

      Its called google mate!

    34. Re:The sad thing is . . . by plague3106 · · Score: 1

      Again, easier for you... For the user this approach means tens or hundreds of applications that have their own update methods (some need to be started, some want you to click 'update' somewhere, etc.) with different UIs for the updating.

      Yes, I can see how the act of simply starting the program is more complex for the user. Actually most programs today on Windows check for updates and / or install them themselves. Acrobat does this, Firefox does this, Windows itself does this.

      It also means security implications as the user now has X additional programs that are connected to the internet.

      I can't speak for other programs, but I know that my updates are safe. Updates have to be signed by a publisher certificate so as long as that is safe, no one can spoof my application. Its one of the features MS added to the .Net framework. Read up on ClickOnce deployment.

      Stand-alone installers have some good properties compared to package management. update deployment is not one of them.

      Yes, because its very intiutive to go to an unrelated application to update another application. Oh, you might also be interested to know that your 'stand alone installers' aren't stand alone. Windows DOES have a package manager, Windows Installer. Can you go to it and ask it to find updates? Yes, if the application developer set that up. Unfortunately many do not.

      I'd also point out though that package managers on linux also suffer similar problems. I would have loved to just click a button to update. It was never that simple. Usually, I had to install updates from their source. Now THAT'S a great user experience, huh? Please, don't act like Linux has the ultimate package management; it does not.

    35. Re:The sad thing is . . . by plague3106 · · Score: 1

      Good! Does the installer ask any questions? If so, does it explain what the questions mean, what the consequences of each answer are, and what answer one should pick?

      Yes, it says do you want to Install? If they click no, nothing happens. If they click yes, the application downloads, installs and runs. No options.

      Ooh, spyware! Or, at least, it could be...if it's closed source and it connects to your website, without me telling it to, how do I know it's only checking for updates?

      Updates need to be signed by the same publisher certficate as the previous installation. It does connect to the update sight automatically. It then says "There's an update. Do you want to install or skip?" I didn't write the installer; its call ClickOnce, and its part of the .Net 2.0 framework. Go read more yourself.

      Yesteryear, the same was being said about Java. The same has been said about DirectX, Internet Explorer 5.5, Winsock, etc. What it really means is that you're targetting what happens to be the Latest and Greatest (C)(R)(TM) API from Microsoft, which they will have to support in length of ages to retain binary compatibility. What will happen when Vista is released, with more Latest and Greatest APIs? Will all of these be provided on older Windows versions, too?

      You don't know anything about the .Net framework do you? First, MS is installing it by default with Win2k3 and above. Windows update has been installing it on WinXP. You can run many versions of the Framework side by side and they do not interfere with each other, also unlike Java. When Vista is released, it will have all versions of the framework (1.0, 1.1, 2.0). You do realize that .Net becoming the new kernel API right? Just like MS released Win32s so that people could target Win9x without abandoning 3.1x users.

      But does Windows on Alpha or PowerPC provide binary compatibility with x86? The ability to run win16 apps on win32 uses a compatibility layer baked into the hardware, as well.

      Yup. You already seem to know why as well, so I wonder why you even asked this question. Oh, the ability to run win16 apps wasn't 'baked into the hardware.' You don't know much about developering on Windows I guess.

      Right, because you're compiling to virtual machine code. The same trick works on any other operating system, of course.

      So that means that you can do it on Windows is irrelevent?

      I guess not. That must be why a lot of software for Linux (if it's not included in popular distros) is shipped in a single (click and run, depending on your distro) binary, much like the installers Windows software uses. Takes some effort from the developer, sure, but I don't think Windows installers come out of thin air either (but I couldn't know, I've never developed for Windows).

      Except it doesn't work as well as Windows Installers. RPM hell is magnitudes worse than DLL hell ever was. My installers is easy; all I do is point a simple program to my exe and tell it a publisher certficate, and it creates the necessary files. I then drop them on a network share, web server, cd rom.. whatever I want. Very easy. Other installers of course require more work.

      You're not alone, and this is a real problem, and it probably won't be going away. Getting compilation to Just Work across a wide variety of platforms isn't easy. Since getting binaries to Just Work depends on getting that, it's even worse. I'm just saying: keep in mind that comparing a single version of Windows on a single machine architecture to a multitude of Linux distros on a multitude of machine architectures is comparing apples and oranges.

      Which is one of the problems with developing for Linux. Too many targets. With Windows, you have Win9x or NT to target. Also, MS got this right with the .Net framework. As a developer, I can target any version of the framework I want. Certain features of the framework (like

    36. Re:The sad thing is . . . by plague3106 · · Score: 1

      That's because the 286 -> 386 change was within the same architecture. Parent is talking about nontrivial architecture changes (such as from x86 to PPC or the like).

      Nope. because he specifically said moving from 32 bit to 64 bit ("AMD64 anyone?").

      Erm... "on 64-bit?" Meaning, your 32-bit application runs on a 64-bit chip with 32-bit emulation/native support? Gee gosh!

      Actually no. See, my app is built on the .Net framework, so an int is always 32 bits, no matter what platform I'm on. And yes, the framework exists on x86, IA64 and NATIVE x64.

    37. Re:The sad thing is . . . by 14CharUsername · · Score: 1
      The second problem is that while I believe Linux is better, for most people it simply doesn't matter. If the computer does what you want it to do, why bother switching? What compelling reason are you going to give a Windows user to switch?

      After a virus scare, and finding a crapload of spyware installed, a friend of mine became very interested in linux.

    38. Re:The sad thing is . . . by 14CharUsername · · Score: 1
      And where's the central repository of knowledge that tells me what's the best text editor of the 9,000 available for Linux.

      Ubuntu Forums.

      Actually, its really no different from windows in discovering what software is best for you. The main advantage of using a repository is that iif your friend recommends a P2P app, and your friend happens to be a complete idiot, the worst case scenario is that you have go into your package manager. With windows the worst case scenario, is, well, much worse.

      It seems the biggest complaint about linux is that its different. I'm not sure how you expect Linux to change this. They can't just name the CD burning program "Nero" so that windows users will know what to use, since Nero is trademarked. The default action when I put in a CD-R is that it will ask if I want to burn a Audio CD or a Data CD and then it opens the suggested program for that. Applications->Accessories->Text Editor opens the suggested text editor. If the suggested apps don't have the features you need, well then the prcess is similar to when Nero or Notepad doesn't support a feature you need. You just ask around (online and offline).

      I guess your problem is that you have all this knowledge about what programs do what in windows and that knowledge doesn't apply to linux. It will never apply to linux because linux isn't windows. If you can get past this, then you will find that linux is as good, if not better, than windows. But you have to let go of that windows-specific knowledge and be willing to learn the things that are linux-specific.

    39. Re:The sad thing is . . . by Phisbut · · Score: 1
      And where's the central repository of knowledge that tells me what's the best text editor of the 9,000 available for Linux? The best media player, the best burning software? How do I know how stable they are? Will they have the functions I need? These aren't hits against Linux at all, but it's a lot easier for me to ask the guy next to me what he uses to burn CD's rather than look it up online.

      I just asked the guy next to me what he uses to burn CD's, and he said he used K3B. So I launched synaptic, and installed K3B. What's your point?

      --
      After 3 days without programming, life becomes meaningless
      - The Tao of Programming
    40. Re:The sad thing is . . . by MarkAD88 · · Score: 1

      Windows does have a central repository of software and hardware that is availble for it. It's not 100% inclusive of course because the sheer volume would be astounding. It does however list a fairly large portion of the more mainstream software that people might want to get their hands on.

      It's called the Windows Catalog and there is a link to it in the Start Menu under All Programs right there next to the link to Windows Update.

      If memory serves correctly it has been there since the first version of Windows XP.

    41. Re:The sad thing is . . . by RAMMS+EIN · · Score: 1

      ``Whats wrong with this? All of a sudden retail starts screaming because they just got cut out of the deal. CompUSA, Circuit City, Best Buy, Wal-Mart, Office Depot, Office Max, Staples, Mom & Pop's software shop in who knows where USA.
        The OTHER problem is this...who decides what goes in the list? What kind of deals get brokered? All of a sudden Microsoft is now controlling WHO I buy my software from? How about the little guy...Small Time Software Company Inc.? Does he then sue to get placed on the list? Can he legally?''

      This is why you need multiple repositories, and a way to change which repositories your system uses. Debian and Ubuntu provide this.

      There is another benefit to this approach as well: repositories could review software before they add it. Thus, by choosing trustworthy repositories, you can get trustworthy software, without the effort or knowledge to conduct reviews yourself. Make the system refuse to run software that has not been approved by any of these repositories and you've got pretty decent protection against all sorts of malware.

      --
      Please correct me if I got my facts wrong.
    42. Re:The sad thing is . . . by Jussi+K.+Kojootti · · Score: 1
      I haven't "acted like Linux has the ultimate package management". I only discussed central package management vs. every-program-for-itself method. I'm fully aware that the package management solutions available in Linux are not perfect (in fact I think they're in many situations quite broken). That shouldn't stop me from criticizing something I believe is inferior from the get-go, should it?

      Actually most programs today on Windows check for updates and / or install them themselves. Acrobat does this, Firefox does this, Windows itself does this.
      ...and ad-aware, and Thunderbird, and Nero, etc. That was the problem I was addressing -- how is the user supposed to remember how and if specific programs are updated?
      I can't speak for other programs, but I know that my updates are safe.
      I'm sure your program is very secure since you said so, but what about the hundred others? Are their updates signed? How is the user supposed to evaluate that?
      I'd also point out though that package managers on linux also suffer similar problems. I would have loved to just click a button to update. It was never that simple. Usually, I had to install updates from their source. Now THAT'S a great user experience, huh?
      Package management model naturally breaks if you want something not yet available in the repositories, this is the achilles heel of course... The good thing is that in that situation you can install software with whatever method you like: binary installer blobs or compiling from source -- just like on the every-program-for-itself install method. What's your point?

    43. Re:The sad thing is . . . by SiChemist · · Score: 1

      Your users don't have to download autopackage. They just run the installer that you generate.

    44. Re:The sad thing is . . . by plague3106 · · Score: 1

      I haven't "acted like Linux has the ultimate package management". I only discussed central package management vs. every-program-for-itself method. I'm fully aware that the package management solutions available in Linux are not perfect (in fact I think they're in many situations quite broken). That shouldn't stop me from criticizing something I believe is inferior from the get-go, should it?

      You have a fundamental misunderstanding of the Windows platform though. Windows includes 'package management,' and the Windows Installer API is actually very advanced. Now if developers don't take advantage of that, who's fault is that? Do you blame the developer on Linux when they DON'T make an RPM? Is it MS' fault they don't make installers for everyone that builds software for their platform? Contrary to your belief, Windows isn't 'every program for itself.' ...and ad-aware, and Thunderbird, and Nero, etc. That was the problem I was addressing -- how is the user supposed to remember how and if specific programs are updated?

      All of those apps have their own update mechinism that usually prompts the user about updates when the program is started. So which is better? The user having to find if there are updates on their own, or the program proactively telling the user about updates? I think the latter is more user friendly personally.

      I'm sure your program is very secure since you said so, but what about the hundred others? Are their updates signed? How is the user supposed to evaluate that?

      Mine is secure because I use a built in feature of the .Net framework. And yes, any other application which deploys via ClickOnce is just as secure. The best part is that its not my own custom process. Just like I wouldn't roll my own encryption, I'm not going to be so arrogant to believe that I know how to write a secure, automatic updating mechinism. FWIW, they don't know that updates on Linux are secure either do they? I seem to recall a few months / years ago about Debian's package servers being compromised...

      Package management model naturally breaks if you want something not yet available in the repositories, this is the achilles heel of course... The good thing is that in that situation you can install software with whatever method you like: binary installer blobs or compiling from source -- just like on the every-program-for-itself install method. What's your point?

      My point is that, except for open source programs targeting Windows, you'll ALWAYS have a Windows installer package to install an app on Windows. On Linux, its a crap shoot, and the time you have to wait for someone to make the RPM can be quite long indeed.

    45. Re:The sad thing is . . . by loqi · · Score: 1

      Nope. because he specifically said moving from 32 bit to 64 bit

      That's a much bigger difference than 286 -> 386. It's just that AMD64 also happens to support the old 32-bit applications. At any rate, the point here is that Windows doesn't "support" the architecture difference, it's done at the hardware level.

      Actually no. See, my app is built on the .Net framework, so an int is always 32 bits, no matter what platform I'm on.

      So wait, as a point in Windows' favor you claim that your app runs "on 64-bit" without issue, then admit that it's actually running on the CLR? That's all well and good... for the CLR. .NET isn't exclusive to Windows; I could say the same thing about my Python application, but that wouldn't be a point in Debian's favor. Java programmers have been enjoying this luxury for years, but clearly the discussion is only relevant to native applications, not those built on explicitly cross-platform VMs.

      --
      If other reasons we do lack, we swear no one will die when we attack
    46. Re:The sad thing is . . . by loqi · · Score: 1

      Users don't want to worry about compling at all, so unless developers make their installers do it behind the scenes with 90% reliablity (which as you say is very hard) they're not going to come to linux.

      This is a false dilemma. You're asserting the advantages of Windows and .NET simultaneously to make a point about Windows applications, but anyone who's developed a .NET application doesn't need to recompile it for Linux.

      --
      If other reasons we do lack, we swear no one will die when we attack
    47. Re:The sad thing is . . . by plague3106 · · Score: 1

      The vast majority of programs for Linux though are not .Net, and thus do suffer the problem I'm talking about.

      Also pretty much all of non-.Net Windows programs come with installers as well.

      So I guess my answer is take .Net out of the equation, and you still have the problems I described.

    48. Re:The sad thing is . . . by plague3106 · · Score: 1

      That's a much bigger difference than 286 -> 386. It's just that AMD64 also happens to support the old 32-bit applications.

      286 -> 386 was also a move from 16 bit to 32 bit, so I don't see how 32 -> 64 is a 'much bigger difference.'

      At any rate, the point here is that Windows doesn't "support" the architecture difference, it's done at the hardware level.

      This is not true. You can install 64 bit Windows and run applications compliled for 32 bit Windows. It does this via the WoW (Windows on Windows) compatability layer.

      So wait, as a point in Windows' favor you claim that your app runs "on 64-bit" without issue, then admit that it's actually running on the CLR?

      My point was that Windows comes with the .Net framework, which makes it irrelevent how many bits the underlying hardware is. This was to counter the claim that I had to recompile my app for 64 bit.

      That's all well and good... for the CLR. .NET isn't exclusive to Windows

      Yes and no. I haven't tried porting anything to Mono, so I don't know how far along Mono is. From what I understand though, System.Security and System.Windows.Forms are missing.

      I could say the same thing about my Python application, but that wouldn't be a point in Debian's favor.

      I would say no, but because Python may or may not be included standard with RedHat, Ubutana (whatever), Slack, etc.

      Java programmers have been enjoying this luxury for years, but clearly the discussion is only relevant to native applications, not those built on explicitly cross-platform VMs.

      Sort of. Java leads to write once test everywhere, as we've seen. The difference though is that .Net isn't just a VM, its end goal is to replace the Win32 API completely. I don't know of anything in the Linux world that has a similar goal.

      As a developer, I am certain that going forward the .Net framework will be shipping with Windows. I know that I can target ANY version of it I want. Java apps even break across the same version but different platforms, let alone across version changes.

    49. Re:The sad thing is . . . by gfxguy · · Score: 1

      Of course I agree with you, but tell him that in order to avoid spyware and viruses he'll have to give up his favorite programs and access to certain kinds of web content (like wmv files), and most people would rather take their chances.

      It IS a compelling reason for me (and your friend), but not for most people. I have this experience all the time - people complain their computer is getting slower and slower, and I know it's because it's bogged down with useless crap that gets automatically run on startup and spyware, and I say "Gee, I don't know, I've never had that problem with Linux." and they don't bat an eye...

      It's hard enough trying to get people to use something besides IE. As soon as I mention "of course, there might be site here and there that won't work with Firefox, but it's not Firefox's fault." They don't care... they don't feel that the benefits outweigh the negatives. Plus we go back to my first reason: it's not MS! Sure, you can do everything, but it's different. I'll have to learn new things! You can't make me learn new things!

      We keep talking about the "average" user. With the computers being pretty much ubitquitous, the average "user" is simply the average "person." The average person can't name a supreme court justice or their representative in congress, and you want them to learn how to use Adblock or NoScript in Firefox? Nah, too much work.

      --
      Stupid sexy Flanders.
    50. Re:The sad thing is . . . by loqi · · Score: 1

      This is not true. You can install 64 bit Windows and run applications compliled for 32 bit Windows. It does this via the WoW (Windows on Windows) compatability layer.

      Fair enough.

      My point was that Windows comes with the .Net framework, which makes it irrelevent how many bits the underlying hardware is.

      That's a weird point to make, unless you're claiming there's no need for native code any more.

      This was to counter the claim that I had to recompile my app for 64 bit.

      That was not the claim. The claim was that Windows' binary compatibility advantages were lessened by foreign architectures. You then explained that your app runs on 64-bit systems no problem, which was not related to the binary distribution vs source distribution discussion.

      I would say no, but because Python may or may not be included standard with RedHat, Ubutana (whatever), Slack, etc.

      Well, if I package my program for Debian, it really doesn't matter whether or not Python comes standard with the distribution, it'll get picked up as a dependency automatically.

      The difference though is that .Net isn't just a VM, its end goal is to replace the Win32 API completely. I don't know of anything in the Linux world that has a similar goal.

      This would be more accurately phrased "Microsoft's goal is to replace the Win32 API with .NET" (btw, good for them!). Of course nothing in the Linux world has a similar goal, any more than Microsoft has any goal to replace the Linux kernel API: both are ridiculous non-goals. Or did you mean something else? Technically Java isn't just a VM either, if you're counting things like cross-platform compatibility layers on top of the various OS services (sockets, threads, etc) as separates-the-men-from-the-VMs kind of features.

      Java apps even break across the same version but different platforms, let alone across version changes.

      I was merely using Java as historical precedent, I would never assert its superiority to .NET.

      --
      If other reasons we do lack, we swear no one will die when we attack
    51. Re:The sad thing is . . . by plague3106 · · Score: 1

      That's a weird point to make, unless you're claiming there's no need for native code any more.

      There is. One of the lesser known features of .Net is that you can ngen your code, which will take the IL binary and convert it into an actual native binary. All the assemblies that come with .Net are ngened in this way. The nice thing is that if you do develop on .Net and Windows (as I don't think there's an ngen for Mono) you KNOW this is avaiable.

      Largely though you don't really need native apps anyway.

      That was not the claim. The claim was that Windows' binary compatibility advantages were lessened by foreign architectures. You then explained that your app runs on 64-bit systems no problem, which was not related to the binary distribution vs source distribution discussion.

      Well, with WoW and the .Net framework, distributing binaries is easier, regardless of 'foreign architectures.' Both of those allow me to distribute binaries without worrying about the architecture. OTOH, distributing source with a make file, a developer DOES have to worry about not only different architechtures, but with Linux, different distributions as well.


      Well, if I package my program for Debian, it really doesn't matter whether or not Python comes standard with the distribution, it'll get picked up as a dependency automatically.


      But that doesn't help you get your application to RedHat, Mandriva, etc. This actually highlights my points I think; even if you package your application, you can't be sure to reach most of the distributions on the platform. With Windows this isn't the case; not only is there only one 'distribution' but MS has been working hard to make your app work with the current versions.

      This would be more accurately phrased "Microsoft's goal is to replace the Win32 API with .NET" (btw, good for them!). Of course nothing in the Linux world has a similar goal, any more than Microsoft has any goal to replace the Linux kernel API: both are ridiculous non-goals. Or did you mean something else? Technically Java isn't just a VM either, if you're counting things like cross-platform compatibility layers on top of the various OS services (sockets, threads, etc) as separates-the-men-from-the-VMs kind of features.

      MS' goal in replacing the current API is to cut down on common programming mistakes, like memory leaks and buffer overflows. I don't think that's a bad goal personally.

      I was merely using Java as historical precedent, I would never assert its superiority to .NET.

      I'm not sure if you're being sarcastic or not. I also didn't mean to sound as if I was bashing Java. I would like to learn it personally. There are differences, and there are things in .Net that would be nice in Java, but I don't think its 'inferior.' My point was that by targeting the framework, you can target more than one architecture (like in Java) and still distribute binary applications.

    52. Re:The sad thing is . . . by loqi · · Score: 1

      There is. One of the lesser known features of .Net is that you can ngen your code, which will take the IL binary and convert it into an actual native binary.

      That doesn't necessarily solve the problem: a bottleneck in .NET might well stay that way when ngen'd.

      Largely though you don't really need native apps anyway.

      No argument here, although I'd like to make the distinction between "native apps" and "apps with some native code". The latter is much more likely to be necessary than the former.

      But that doesn't help you get your application to RedHat, Mandriva, etc. This actually highlights my points I think; even if you package your application, you can't be sure to reach most of the distributions on the platform.

      Actually, I think your response here highlights what was said earlier by others: Linux isn't a platform. LSB is a platform. Red Hat is a platform. Debian is a platform. I think it's easily conceded that targeting every Linux distribution is a lot of work, unless you're prepared to bundle your dependencies (which is sometimes not a bad way to go, then it's trivial to set up a binary installer). Personally, although it goes against "the Linux way" in some respects, I'd love to see Ubuntu or some other Debian-derivative become the de facto standard Linux distribution, just to quell this "targeting Linux is so hard!" meme. Anyway, distributing the source and a good binary installer is a great way to encourage both end-user installation and package-writing by the various distribution maintainers.

      MS' goal in replacing the current API is to cut down on common programming mistakes, like memory leaks and buffer overflows. I don't think that's a bad goal personally.

      Certainly isn't! Coming from the Win32 API and MFC, I was shocked at how well-designed the .NET framework is by comparison. Microsoft has come a long way from those nightmarish systems. Moving the OS interface proper away from lower-level languages is less of a concern to me, as higher-level languages usually provide a clean wrapper on top of it.

      I'm not sure if you're being sarcastic or not.

      Definitely not. I border on a Java anti-zealot, probably because of how overrated I feel it is. Although I wish C# were less Java-esque, it's at least step in the right direction if you are going to blatantly copy it. And the advent of IronPython means being "stuck" developing in a .NET environment is infinitely preferable to its Java counterpart.

      But Linux still rocks :)

      --
      If other reasons we do lack, we swear no one will die when we attack
    53. Re:The sad thing is . . . by plague3106 · · Score: 1

      That doesn't necessarily solve the problem: a bottleneck in .NET might well stay that way when ngen'd.

      A bottleneck in a native app will remain also. Doesn't really have to do with source vs. binary distribution.

      No argument here, although I'd like to make the distinction between "native apps" and "apps with some native code". The latter is much more likely to be necessary than the former.

      I'm not even sure that latter group will really be that large either. And if you ngen, you have a 'native' image. Still runs within the framework though. If you are getting at that the framework could slow things down, yes, it could. But most apps don't need ever millisecond of performance; games and realtime apps are the only two I can think of. Even then though there's a managed API for DirectX too, so the feelign I get from MS is that even high performance games can be written in .Net.

      Actually, I think your response here highlights what was said earlier by others: Linux isn't a platform. LSB is a platform. Red Hat is a platform. Debian is a platform. I think it's easily conceded that targeting every Linux distribution is a lot of work, unless you're prepared to bundle your dependencies (which is sometimes not a bad way to go, then it's trivial to set up a binary installer).

      Which was what I was trying to get at, although that doesn't really affect teh source vs. binary distribution methods.

      Personally, although it goes against "the Linux way" in some respects, I'd love to see Ubuntu or some other Debian-derivative become the de facto standard Linux distribution, just to quell this "targeting Linux is so hard!" meme. Anyway, distributing the source and a good binary installer is a great way to encourage both end-user installation and package-writing by the various distribution maintainers.

      Agreed, which was one of the points I was making; I don't really need to release source if I choose not to for Windows. It pretty much will be easily installable by your average user. The various Linux distros attempt to replicate that ease, but the problem is the many distributions all doing things their own way. That actually makes installing programs on Linux more difficult for your average user.

      I would like a standard distro as well.

      Certainly isn't! Coming from the Win32 API and MFC, I was shocked at how well-designed the .NET framework is by comparison. Microsoft has come a long way from those nightmarish systems. Moving the OS interface proper away from lower-level languages is less of a concern to me, as higher-level languages usually provide a clean wrapper on top of it.

      As was I. As a developer doing VB6 + ASP, I was ready to say fuck it and move to Linux development. At the last minute, I was introduced to .Net. Going back would be torture. :-) That's why I hate when the zealots bash the .Net framework as just a Java rip off or useless. Its actually a great API to on which to develop.

      Definitely not. I border on a Java anti-zealot, probably because of how overrated I feel it is. Although I wish C# were less Java-esque, it's at least step in the right direction if you are going to blatantly copy it. And the advent of IronPython means being "stuck" developing in a .NET environment is infinitely preferable to its Java counterpart.

      Didn't want to assume; sacrasm has been biting me a lot lately. I think Java has a lot of good stuff, and I personally like .Net and where its going (looking forward to .Net 3). I actually think Java could benefit in some ways; Attributes and delegates come to mind.

      But Linux still rocks :)

      I agree; I just don't think its ready for me yet. ;-) In all seriousness though, I was running linux, server for years and desktop for fewer years, but had to go back. I don't mind digging, but it started to feel like to get anything done / working I was REQUIRED to do so. And that was just as a user, so I dreading trying to create any apps for it..

  6. Windows Perspective by Tadrith · · Score: 4, Interesting


    I'm a computer geek who regularly uses Windows. Yes, I know, boo, hiss, whatever. My software development happens under Windows because that's what I learned on, that's where most of the market currently is, and that's what I've got a job doing. I'm not going to stop working for a company I like doing what I enjoy just because I happen to do my work on Windows.

    In any case, periodically I load Linux on an alternate hard disk in my machine to play around with it and see what I can get going. I do like to keep my knowledge of it up in the event that I run into it on the job (I also do field work from time to time), but I also like to see how far it has progressed. At some point in time, I really would like to use it as my core operating system, even if I still have to drop into Windows when I work.

    Recently (about a week ago), I decided to try a couple of different distributions. They all seem to suffer from one problem -- the USB keyboard no longer works when it hits the installer. "You forgot to turn on legacy mode for USB in your BIOS!", is the first thing most people would say, except that I haven't forgotten to turn it on. It works perfectly fine for the BIOS-based boot menu. I even triple checked it, thinking I was missing something. I tried numerous options to try and get the damn thing working, to no avail.

    Yes, I could get a USB to PS2 converter and yes, it does work fine after that. But that's not the point -- I shouldn't HAVE to do that. Critical things like that will kill any interest your average user will have in the operating system. But, for what it's worth, I was very pleased with what I saw after I did finally get it loaded. It's come a long way from the operating system I tinkered with 6 or 7 years ago.

    1. Re:Windows Perspective by Anonymous Coward · · Score: 0

      teh freebsd installer has teh option for usb keyboards.
      it asks you if you are using one and just works.
      teh linux don't have nottin on freebsd

    2. Re:Windows Perspective by Anonymous Coward · · Score: 0

      I've installed Linux on a machine with a USB keyboard and it worked just fine. I'm really curious what distro you used, and on what hardware, as this seems rather unusual.

    3. Re:Windows Perspective by Anonymous Coward · · Score: 0
      Critical things like that will kill any interest your average user will have in the operating system.
      Since when does average users install their operating systems?
    4. Re:Windows Perspective by pinchhazard · · Score: 1

      SHOW US YOUR BELLYBUTTON

      --
      Do you love freedom??? Do you love freedom!!! DO YOU LOVE FREEDOM!!!!!!!!
    5. Re:Windows Perspective by RAMMS+EIN · · Score: 1

      ``But that's not the point -- I shouldn't HAVE to do that.''

      You know, not saying you're wrong, but I'm getting tired of hearing this argument. Since when is it not your responsibility that your hardware is compatible with the software you want to run? Windows doesn't support every piece of hardware that Linux supports, either. In fact, I wouldn't be surprised if, say, Ubuntu supported more hardware out of the box than Windows XP.

      --
      Please correct me if I got my facts wrong.
    6. Re:Windows Perspective by Blakey+Rat · · Score: 1

      Bullshit.

      If Linux supports the USB keyboard when it's fully installed, there's no reason that the installer shouldn't except the programmers of it didn't bother to do any sort of QA process what-so-ever.

      If you go to (to use an example) Ubuntu's website, and check the specs, and it says right there in black and white "supports USB keyboards," then that means it should support USB keyboards all-around. If it doesn't, it should say "supports USB keyboards (PS/2 keyboard required for install)" or something that isn't as misleading.

      I don't know what distros he tried, but I've encountered tons of examples of Linux distributions claiming to support things that they didn't actually support. The latest one was probably my WinPVR 250 card that numerous people claimed was supported in Linux, but which never worked despite installing the driver following the exact directions.

    7. Re:Windows Perspective by Tadrith · · Score: 1

      Actually, the keyboard doesn't work at all, regardless of whether it is during the installation, or post-installation. It flat out doesn't work when it's plugged into a USB port. ;)

      Honestly, more than anything, I wish I knew why.

    8. Re:Windows Perspective by howlingmadhowie · · Score: 1

      if you're installing something with proprietary closed-source drivers you can expect it to not work on most linux kernels.

    9. Re:Windows Perspective by RAMMS+EIN · · Score: 1

      ``If Linux supports the USB keyboard when it's fully installed, there's no reason that the installer shouldn't except the programmers of it didn't bother to do any sort of QA process what-so-ever.''

      Right. So we'll mandate that people acquire every possible piece of hardware on the planet before they're allowed to put together a Linux distribution. Because, you know, the Windows installer also supports all makes and models of SATA drive and SCSI controller that an installed Windows supports, without requiring such things as inserting driver disks and the like.

      ``If you go to (to use an example) Ubuntu's website, and check the specs, and it says right there in black and white "supports USB keyboards,"''

      Maybe his keyboard isn't a real USB keyboard? I don't know if this is the case for keyboard, but I know there are standards for certain classes of USB hardware, and I would consider it perfectly acceptible if some OS supported devices that comply with the standard and not devices that didn't.

      ``I don't know what distros he tried, but I've encountered tons of examples of Linux distributions claiming to support things that they didn't actually support.''

      In that case, they're lying, and they deserve whatever liars deserve. I've personally never encountered this, but if you have, you have every right to be outraged.

      --
      Please correct me if I got my facts wrong.
    10. Re:Windows Perspective by ratboy666 · · Score: 1

      So, now I am curious. What motherboard, are you using a USB external hub, if so, which one, and which keyboard?

      Secondary, which distribution(s)?

      YMMV
      Ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    11. Re:Windows Perspective by Tadrith · · Score: 1


      I mentioned the distros in another message, but I'll post 'em here:

      Fedora Core 5
      SUSE Linux Enterprise Desktop 10
      And I tried an old version of Ubuntu (Warty)

      I would really like to use Fedore Core 5, though. I finished getting it running with a PS2 converter, but it still doesn't work with just the USB. From what I've used of it so far, I like it. I know I can just leave it like that, but it's bugging me, and I would like it to work without it. :) I'm not using an external hub, just the ports on the motherboard. I tried using a different port, and that didn't help either.

      My current setup:

      ASUS A8N-SLI Premium Motherboard
      AMD Athlon 64 X2 3800+
      nVidia GeForce 7900
      Creative SoundBlaster X-Fi

    12. Re:Windows Perspective by ratboy666 · · Score: 1

      Tadrith

      I currently on contract with ATI/AMD, but I'll see if I can squeeze out some cycles to look at this (again, I am intrigued). Not tonight, though...

      Ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    13. Re:Windows Perspective by Tadrith · · Score: 1

      Sure.

      I agree, it is a really odd problem. I did a lot of looking on the web, but nothing came of it.

    14. Re:Windows Perspective by lilo_booter · · Score: 1

      I have never had problems with usb keyboards on linux, but on my intel mac... well, every time I boot up, either the keyboard or the mouse of my el cheapo wireless set isn't working.

      Now, my gut reaction would that the particular keyboard and mouse are not compatible with OS/X. The fix will just be to buy a replacement (.. but then, I live in Belgium and good QWERTY keyboards are like gold dust here - I'm just waiting for the next time I'm going to the UK or Holland :-)).

      Just a thought, but have you tried another keyboard?

      FWIW, the same el cheapo set works perfectly on Linux laptop - go figure...

    15. Re:Windows Perspective by Anonymous Coward · · Score: 0

      Try a recent Knoppix CD (no install, just boot from the CD) and see if it works. I've yet to encounter a piece of hardware that claimed Linux compatibility and refuses to work with Knoppix.

    16. Re:Windows Perspective by Tadrith · · Score: 1

      I recently replaced my keyboard for one with low profile keys. I'll have to dig up my old one and try.

      But, it too had similar problems on a different motherboard. I'll try it anyway. :)

    17. Re:Windows Perspective by Blakey+Rat · · Score: 1

      Right. So we'll mandate that people acquire every possible piece of hardware on the planet before they're allowed to put together a Linux distribution.

      That has nothing to do with what I said. What I said is that if the distribution claims to support a particular piece of hardware, they should QA their install process to make sure that particular piece of hardware works. I was assuming when I wrote that that the USB keyboard worked after the distro was installed but (as the original poster replied) it turns out I was wrong about that... so perhaps this statement is wrong and the distro doesn't support USB keyboards at all anyway, in which case you wouldn't expect them to work with the installer any more than the OS itself.

      Because, you know, the Windows installer also supports all makes and models of SATA drive and SCSI controller that an installed Windows supports, without requiring such things as inserting driver disks and the like.

      We're not talking about Windows, we're talking about a Linux distro. This sentence is entirely irrelevant. Why the hell do Linux users always have to bring Windows into everything? It's a sick obsession.

      Maybe his keyboard isn't a real USB keyboard? I don't know if this is the case for keyboard, but I know there are standards for certain classes of USB hardware, and I would consider it perfectly acceptible if some OS supported devices that comply with the standard and not devices that didn't.

      So it's an imaginary USB keyboard? ... ok, snark aside, I understand what you're getting at, but there are two factors here:
      1) Why would someone build a USB keyboard that didn't support the USB standard and (therefore) required special drivers before it worked?
      2) The term "real" here is very misleading. Obviously it's a real keyboard, it's made of plastic and sitting on the desk. What you mean is "standards-compliant" or something similar. And you're right, Linux can't reasonably support this type of keyboard if one exists. (And I doubt any exist.)

      In that case, they're lying, and they deserve whatever liars deserve. I've personally never encountered this, but if you have, you have every right to be outraged.

      The problem with my WinPVR 250 was that every person in Linux-ville assured me, over and over, that WinPVR 250s worked with Linux. It turns out the *truth* is that *some* WinPVR 250s work with Linux, and there's no way to tell (short of installing the hardware and trying out it) which ones do and which ones do not. As mine was way past it's return/exchange date, and there was no way to tell if another would work even if I did exchange it, it turns out that my WinPVR 250 does not work with Linux. Anybody claiming that WinPVR 250s work with Linux without mentioning that only some do is lying, IMO.

      I've had other bad experiences, but they're pretty old and out-of-date. (RedHat 6.2 claiming to support my Soundblaster 128 then not producing any sound, for example. I think there were a couple others, but I'd have to go back and look at my notes.)

    18. Re:Windows Perspective by Anonymous Coward · · Score: 0

      I will add that I have not had this issue myself with a USB keyboard in the past two or three years. My secondary computer uses a USB keyboard with USB mouse and I have installed all manner of open source operating systems on it over the years. Gentoo, Ubuntu, Debian, FreeBSD, Fedora and a host of minor Debian derivatives. The only one that failed was OpenBSD, which I was somewhat heartbroken over. Which, regardless, was not related to the USB keyboard not working.

      I just installed Debian stable on it over the weekend. Yes, crusty old Debian stable. I used the 2.6 kernel (linux26 boot option), but I know 2.4 has worked in the past. The thing uses XFree 4.3 for crying out loud! There's a reason I call it Debian "ancient." Yet even then it still works fine.

      Now, I did have an issue with Knoppix derivatives where the mouse would fail. But that was on a completely different machine and it was the mouse, not the keyboard. It seemed like every debian knock-off that relied on Knoppix for device detection was affected. Then Ubuntu started using discover and I told all of those knoppix kids to fuck off. Haven't looked back.

    19. Re:Windows Perspective by Anonymous Coward · · Score: 0

      Ah, yes. I recently exchanged my PS/2 keyboard for a USB keyboard. Windows 2000 no longer booted. Sarge didn't care.

    20. Re:Windows Perspective by RAMMS+EIN · · Score: 1

      ``That has nothing to do with what I said. What I said is that if the distribution claims to support a particular piece of hardware, they should QA their install process to make sure that particular piece of hardware works.''

      But they didn't claim to support _that_ particular piece of hardware, they (allegedly) claimed to support "USB keyboards". The unfortunate user has a single USB keyboard that doesn't work. You claimed this meant the distributor didn't perform "any QA process whatsoever". Apparently, to have performed "any QA process whatsoever", they should have tested using that particular USB keyboard. But, since they can't know what particular USB keyboard someone is going to be using, they would have to test with all of them. Ergo, they would have to acquire all of them.

      ``We're not talking about Windows, we're talking about a Linux distro. This sentence is entirely irrelevant. Why the hell do Linux users always have to bring Windows into everything? It's a sick obsession.''

      Normally, I would agree with you. However, in this case, the discussion is about Linux vs. Windows. So, no, it's not my sick obsession; it's being on topic.

      ``1) Why would someone build a USB keyboard that didn't support the USB standard and (therefore) required special drivers before it worked?''

      I always wonder about that, too. Still, there's no shortage of devices that work differently from every other device of the same type, meaning they all need a driver specific to that device. It's one of my pet peeves, actually.

      ``2) The term "real" here is very misleading. Obviously it's a real keyboard, it's made of plastic and sitting on the desk. What you mean is "standards-compliant" or something similar.''

      Right. Thanks for pointing that out. I was saying "real USB keyboard" as in "USB keyboard, as defined by the [assumed to exist] standard for USB keyboards". "Standard-compliant" would have been a better choice of words. By the way, I just looked it up, and there is indeed such a standard: USB keyboards belong to the HID class. Linux has a single driver for compliant keyboards.

      ``And you're right, Linux can't reasonably support this type of keyboard if one exists. (And I doubt any exist.)''

      I think they do exist and the original poster has one. After all, if his keyboard were standards-compliant, how come it fails to work with the Ubuntu installer, given that other keyboards _do_ work with it?

      ``Anybody claiming that WinPVR 250s work with Linux without mentioning that only some do is lying, IMO.''

      Hmmm, well, not in my interpretation of the word "lying": WinPVR 250s _do_ work with Linux, as they asserted. Just not all of them. So they're not telling you the whole truth. They are definitely misleading you. But what they're saying is not false. As a side note: don't you just hate it when manufacturers make different, mutually incompatible devices, and stick identical names on them? How are we supposed to know what we're buying, that way?

      Anyway, it still sucks if _your_ device is not supported, even though the information you gathered before finding out indicated that it would be.

      --
      Please correct me if I got my facts wrong.
    21. Re:Windows Perspective by level_headed_midwest · · Score: 1

      IThe problem stems from the fact that the ISOLINUX used to boot the live CDs and installers does not load USB modules- USB detection and support is done by coldplug later in the boot sequence. Windows loads the drivers into its "live kernel" right when it starts up- that's why it takes minutes to get to do anything after you stick in a Windows CD to install but the Linux boot prompt shows up immediately. If you want to get this fixed, perhaps the guys that do ISOLINUX need to be contacted to load some USB HID drivers on boot instead of relying on the host computer using PS/2 or a USB -> PS/2 emulation at boot in the BIOS.

      --
      Just "gittin-r-done," day after day.
    22. Re:Windows Perspective by Blakey+Rat · · Score: 1

      As a side note: don't you just hate it when manufacturers make different, mutually incompatible devices, and stick identical names on them? How are we supposed to know what we're buying, that way?

      It doesn't matter, because (regardless of the sub-model of device) they all work flawlessly in Windows. The OS they're advertised to work with.

      The problem is the Linux users who lied to me about their working, when at least one of the people who told me this KNEW that not all WinPVR 250 cards works. All the IVTV (the driver required) documentation also lies about this, even though you can find out the truth if you dig around in Google. Of course, the IVTV docs haven't been updated since (apparently) 2001 because all the directions are either incomplete or plain wrong, but still.

      Anyway, it still sucks if _your_ device is not supported, even though the information you gathered before finding out indicated that it would be.

      Yes it does. It also sucks that so many people wasted my time telling me my computer would make a perfect MythTV box with hardware I already owned when, as it turns out, this hardware doesn't work at all in Linux.

      (PS: Yet again Slashcode has treated the Submit button as the Preview button in Safari. Fix this bug already! Christ.)

    23. Re:Windows Perspective by 14CharUsername · · Score: 1

      They may not have been intentionally misleading you. I have a video capture card and if someone asked me if it worked under linux then I would say yes. Then if it later came out that there were different versions of that card being sold under the same name I suppose you could say I was misleading you. But it would be more accurate to say the manufacturer was misleading you by saying that your card was the same as my card when it wasn't.

      Not sure why you'd blame Linux for lying to you when it was the manufacturer that lied to you. If I say that linux supports widget-2000 and then someone makes a completely different product named widget-2000 that isn't supportted by linux, does that make me a lier? I'd say the manufacturer is lying by claiming their product is a widget-2000 when it isn't.

      Just checking the the ivtv supported hardware page there appears to be four different PVR-250s that they say will work. Is your card one of those? If you've tried to get it working recently or if your card is a different version from the ones they have listed maybe you could let them know so they can update the page.

    24. Re:Windows Perspective by Blakey+Rat · · Score: 1

      But it would be more accurate to say the manufacturer was misleading you by saying that your card was the same as my card when it wasn't.

      But it is the same. It does the exact same thing in Windows in the exact same way. That's like claiming that Apple's switching their OS from PPC to x86 makes it an entirely different OS that should go in a different box... no, it doesn't work that way in the real world. Maybe it does in fantasy-Linux-land, but in the real world nobody gives a crap what specific chips are soldiered on the board, just how it works.

      Just checking the the ivtv supported hardware page there appears to be four different PVR-250s that they say will work. Is your card one of those? If you've tried to get it working recently or if your card is a different version from the ones they have listed maybe you could let them know so they can update the page.

      It wouldn't do any good, because as I said before, the only way to tell if you have a "good" one or a "bad" one is to actually install it and IVTV and see if it works. Like I've been saying, all WinPVR 250s work the exact same in Windows regardless of whatever minor hardware change they made that the IVTV people couldn't cope with.

      Anyway, it was like a year and a half ago. I don't even have my PC set up anymore.

      (PS: For the third time this morning, the Submit button acts like the Preview button in Safari.)

    25. Re:Windows Perspective by ratboy666 · · Score: 1

      Ok, the issue is isolinux not having the approporiate usb driver, coupled with BIOS problems. The solution is a BIOS upgrade -- download and flash the BIOS on your motherboard. Sorry for the delay in answering the problem...

      It only affects installation; after Fedora Core is running, it will (should) be just fine.

      Ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    26. Re:Windows Perspective by Tadrith · · Score: 1

      After I had Fedora running, it still would not work. Unfortunately, there's no updates for my BIOS, either.

      Last night I tried Ubuntu Dapper Drake, and everything works great, though. So I'm going to stick with that. Thanks for the assistance, though. :)

    27. Re:Windows Perspective by 14CharUsername · · Score: 1

      If it was exactly the same then it would work, wouldn't it? There are different hardware revisions of that model. At the time you tried it the particular revision you had didn't work with ivtv. It is highly likely that that revision was made after the driver was written for linux. You can't really expect the developers to be able to see the future can you? And before you revision of the card was released PVR-250 was supported. The manufacturer released a different revision that wouldn't work with the linux driver.

      And of course it worked under windows. They would have made changes to the windows driver before release to make sure they it wwould work. The manufacturer did not do the same with the linux driver. Again the fault lies with the manufacturer for not giving you the support you needed.

      And as far as I can tell the PVR-250 appears to be fully supported by ivtv now. Yes there is a lag between when a new piece of hardware is released. You have to realise that the manufacturer isn't writing the drivers, often times it is a group of volunteers that are writing it from specs (if they're lucky) or by reverse engineering (if they aren't). Now it would be nice if on the package it said PVR-250c so that if you asked around, people would tell you that PVR-250a and PVR-250b are supported while PVR-250c is not. It is so easy for the manufacturer to do this, just a simply little change of packaging. But they didn't do that so you end up with PVR-250 and unless you're psychic there is no way to know if its rev a, b, or c. If the manufacturer doesn't mark it on the package, then the only way is to try it out and see if it works.

      Now yeah maybe someone should have told you the situation with the different revisions and the poorly marked packaging. But it is likely that the person you spoke to wasn't aware of the existence of the different hardware revisions. All the dude knew was that he knew some people that had the PVR-250 working under linux and he just relayed it to you. I seriously doubt that someone knew that your PVR card wouldn't work and lied to you about it. What would motivate someone to do that?

    28. Re:Windows Perspective by westlake · · Score: 1
      Since when is it not your responsibility that your hardware is compatible with the software you want to run? Since the day when a Windows driver began to ship with everything from a SOHO office printer to an Orion telescope and a Singer sewing machine.

  7. There is no "Linux operating system" by RAMMS+EIN · · Score: 1

    This is a nice illustration of what I mean when I say there is no such thing as "the Linux operating system". There is, however, "the Debian GNU/Linux operating system" and "the Fedora Core operating system" (as well as "the Windows operating system" and "the OpenBSD operating system").

    --
    Please correct me if I got my facts wrong.
    1. Re:There is no "Linux operating system" by Burz · · Score: 1

      GNU/Linux IS an operating system, and it is standardized, but it doesn't have any "handles" that end-users can (or would want to) grab hold of. So the ones that try to use it get a distro, with all sort of non-standard (non-LSB) stuff like X11, a window manager and the like.

      What Linux isn't is a PC platform. MacOS and Windows are PC platforms, NOT mainly because of their GUIs are standardized (in fact, they shift in usually understandable ways). Its because you can learn to program complex applications on Windows/Mac, and expect a relatively stable platform where other people can easily acquire and run your stuff when you start to get really ambitious. They are mediums of creativity that produce applications which draw users to those platforms.

      Linux distros comprise a desert of shifting sand by comparison. Its too hostile for anyone to thrive off it except for career geologists and the like. In our case, Linux is like a candy store for system-level coders and admins, and things are standardized mainly for their benefit and convenience. Rarely, we will get a system hacker who has some skills in writing higher-level functionality, but even so they have spent too much in time/experience/habit into lower layers and lack the experience to compete.

      Also, how do they offer tech support when the underlying OS could be different in so many ways? The answer is usually either A) reduce capabilities/ambition of your code and rely on mainly common system services, or B) give it to the repository priests (for free) and let them stand between you and your users (instead of forging more direct relationships with them).

      LSB Desktop could be an answer. We'll see.

  8. Which distros? by jonasj · · Score: 1

    Which distros?

    --
    You know, Microsoft's street address also says a lot about their mentality.
    1. Re:Which distros? by Tadrith · · Score: 1

      Well, I downloaded Fedora Core 5 to try it out. I haven't touched anything by Red Hat in some time (I have a habit of using Slackware whenever I play around, for some reason). That was the first one that didn't work. I also tried the evaluation version of SUSE Linux Enterprise Desktop 10. I used to do a lot of work with Novell Netware back in the 4.11 days, so I thought I'd revisit Novell. I also tried Ubuntu, but I used an older version that I had lying around (Warty), so that's not exactly the best test.

      Interestingly enough, FreeBSD also has a problem, though it will work once the installation is finished.

      For all I know, it may be something with my motherboard that isn't working right that Windows is just working around.

    2. Re:Which distros? by Anonymous Coward · · Score: 0

      If you have teh time, try installing windows from scratch on that PC. And may god be with you (and have a floppy drive) if you need to install RAID drivers.

    3. Re:Which distros? by Anonymous Coward · · Score: 0

      Check out nLite.

    4. Re:Which distros? by cloricus · · Score: 1

      He doesn't want to install RAID he wants a simple USB keyboard to work. I've noticed this with several USB keyboards recently with friends complaining though I've never had it myself with the hundreds of keyboards I've installed Linux on...I can only assume it is a specific dodgy chip being used or some thing just off about the keyboards in question and changing distro's doesn't really seem to fix it. In the cases I've seen of it I've recommended that the user just buy another USB keyboard which has fixed the problem every time - small investment to make and I'm sure it pays off in TOC pie charts some where. :P

      --
      I ate your fish.
    5. Re:Which distros? by Tadrith · · Score: 1

      Yeah, I've found a couple references to problems with it from other people.

      I downloaded the latest Ubuntu today, to try that. I was extremely pleased to find that everything works fantastic, including my USB keyboard. Must just be a distro thing... but I think I'll stick with Ubuntu. Been a while since I saw it lst, and from what I've seen so far, I'm liking it even more than Fedora. Based on the other comments to my post, I think Debian-based distros like my computer better.

    6. Re:Which distros? by ErroneousBee · · Score: 1

      I had problems with a USB keyboard about 1 year ago (Knoppix and Gentoo but not Mandriva2006). It has since dissapeared (Gentoo, Suse and Ubuntu all worked as far as the keyboard was concerned.)

      --
      **TODO** Steal someone elses sig.
    7. Re:Which distros? by 14CharUsername · · Score: 1

      Most likely Ubuntu has a newer version of the kernel that can detect and work around something weird in your USB keyboard and/or the USB chipset in your motherboard.

      Anyway, good luck with linux... once you get to know it, you'll probably find yourself wanting to use windows less and less.

  9. LINAPCP - by Burz · · Score: 2, Informative

    "Linux" is not a Personal Computing platform. It's a kernel that's wedded to the GNU toolchain, which is meaningless to most end-users and young developers starting out. Its a boon for people who 'do infrastructure' (including managed thin-clients) or gizmos with custom UIs. But thin-clients != personal computing. This only looks like a platform if you're a sysadmin or systems-oriented coder.

    To anyone just wanting to run their PC, get user-oriented applications on CD or downloaded as a file... or experiment with some code that their teachers and pals across town can download as a file and run... "Linux" (nee Fedora, SuSE, Ubuntu, Linspire, Xandros, etc, etc) feels like a big headache. Your friends are trying out "Linux" too? Well, you've probably got to learn packaging, dependencies, repositories, etc. before you can expect your experiements to run at all on anyone else's system. The fragmented distro scene is like chlorine against budding application developers needing platform stability in order to express their creative urge.

    So in the crucial desktop PC space, Windows and Mac will continue to have a considerable edge.

    People here often forget what makes the PC experience special: The uniformity of a platform aimed at *their* needs (not just those wanting to experiment with new encryption and packet-switching schemes), primarily the ability to install apps and drivers at will (and before you issue the kneejerk response, no Mac OS does NOT suffer by advancing these essential platform qualities).

    Anyone wanting GNU/Linux + Whatever to shine as an alternative for PC users should get behind the new LSB Desktop spec. that is due this December/January. At least then ISVs (not just system hackers) will have something uniform to target as far as APIs and other features are concerned, and we should see more creative and wonderful applications that can draw end users to the platform.

    To those who don't care or hate the idea, perhaps because of the notion that elitism is what keeps GNU/Linux good and secure, I suggest adopting a tolerant and polite attitude instead; No one will be forcing you at gunpoint to use distros conforming to LSB Desktop. The desktop PC needs a workable free alternative, and we're looking to geeks to either help or get out of the way.

    1. Re:LINAPCP - by howlingmadhowie · · Score: 1

      the fragmentation gives linux its vigour. think of it as a boat being pulled by thousands of people. They can't all pull in exactly the same direction, but they get there a lot faster than a boot being pulled by one.

      when windows xp came out, the linux desktops looked like windows 95. Now, when windows vista is coming out, it looks primitive compared with a modern opengl desktop on linux. The linux development model is running rings around apple and windows.

      and btw, you only need stable apis if you want to develop closed source drivers for the kernel. if you want your code to run on someone else's linux box, send it to them as source and they can compile and install it themselves.

    2. Re:LINAPCP - by Burz · · Score: 0, Flamebait

      Doesn't seem all that vigorous from where I'm standing. For applications, its *anemic*.

      A Windows user posted elsewhere that he wanted to try Linux, but having a USB stopped him cold from using the installer. That's not a sign of robustness or vigor. Again, no real obstacle to the admin types who do enjoy robust features in Linux intended for that audience. For everyone else, its the same story: Endless prickly details that must be tended from the CLI before basic things like keyboards, displays and sound not only WORK... but can be RELIED upon.

      What's reliable in Linux is Ethernet, ATA, etc. Interfaces you need to run a headless server.

  10. Re:Not again... by jrieth50 · · Score: 1

    How about FreeBSD on your servers, Kubuntu on your desktop, and Windows on your laptop due to more advanced power management/factory utilities. Works for me, it could work for you. And none of it is incomfortable - as I prefer to use Kubuntu when I'm not away from home and forced to use my laptop. I don't really see the incomfortable argument if incomfortable is indeed a word. And thats running Edgy Eft knot 3 - which was a breeze to install and caused no further complications in system setup.

  11. Crappy hardware by mangu · · Score: 2, Insightful
    Sound, video acceleration, UDMA-support (meaning harddrive-access will be dog slow), bluetooth.


    It's the same thing when people say "XP is rock-solid for me" and I answer "I get plenty of blue screens in XP", they say "the problem is in the device drivers".


    Distributions like Ubuntu, Mandriva, or Suse, which have powerful installers, usually get all the hardware working automatically. Other distros, like Debian, Gentoo, or Slackware normally need a bit of fiddling to get all the hardware working. But if you compare Linux with Windows, hardware which is not quite kosher will give problems in both systems. The difference is that in Linux it will be hard to get to work in the first place, in Windows it will install easily but crash the whole system later.


    Given a choice, the best option is always good hardware, but if I have to live with crappy hardware I'd rather have a system which I can configure to work with the troublesome hardware than with a system that will get the hardware working only to crash on me.

    1. Re:Crappy hardware by alexhs · · Score: 1

      FYI, your AC parent is trolling, Debian works fine out of the box :

      Sound and UDMA support are OK.

      Bluetooth I can't say.

      3D acceleration doesn't work for nvidia and most recent ati cards out of the box, because binary only modules are banned on Debian, and install media won't include non-free section.
      You can get support by including non-free section in your repository and downloading the approopriate package.

      --
      I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
    2. Re:Crappy hardware by glittalogik · · Score: 1

      Bluetooth support on Ubuntu took me (and my el-cheapo USB dongle) one package from the repositories and about 10 minutes of fiddling, probably the same or less time all up than installing the XP drivers that came with it on another machine.

    3. Re:Crappy hardware by Schraegstrichpunkt · · Score: 1
      3D acceleration doesn't work for nvidia and most recent ati cards out of the box, because binary only modules are banned on Debian, and install media won't include non-free section. You can get support by including non-free section in your repository and downloading the approopriate package.

      It does work almost out-of-the-box on Debian, though. (Or, I guess technically, it will work in the next release. It works in etch.) Want the ATI drivers? Run "module-assistant auto-install fglrx" (or the short form: "m-a a-i fglrx").

      Of course, if you're not running on x86, or you're running a bleeding-edge kernel, or a special X server, it might not work (those are the breaks with binary-only drivers), but when it will work, Debian does a great job of streamlining the process.

    4. Re:Crappy hardware by IpalindromeI · · Score: 1

      And for nVidia:
      m-a a-i nvidia

      In fact, it's easier than installing the nVidia drivers on Windows.

      --

      --
      Promoting critical thinking since 1994.
  12. Re:Not again... by Anonymous Coward · · Score: 1, Insightful

    "Bye bye karma..."

    You mean, "bye bye credibility". Just because you never use Linux on the desktop doesn't mean that people who do are uncomfortable doing it. Of the three major operating systems I use daily, I find Windows to be the least comfortable. Does that make me a Linux zealot? or a Mac zealot? or an anti-Microsoft zealot? Or does that make me a person who has an informed opinion and bases his decisions upon that opinion? Hm.

    Well, I guess it all boils down to what it is you want to believe. You clearly have some emotional investment in thinking that using the most common and popular OS makes you somehow more special, better, or more rational than those of us who don't like it. What's not clear is why you feel the need to flaunt your membership in the MS lovers' club, and why you need to taunt people who disagree with you. The only answer I can come up with is insecurity - no, no, I'm not talking about Windows. I'm talking about your psyche. I think you need to get in touch with yourself, learn to know and to like yourself, and then perhaps you'll see that if using Windows defines you as a person, you're not really much of a person. Perhaps after high school, you'll realize that all those cool kids you wanted to hang out with weren't really all that cool, either.

    We're here to help. Come talk to us when you develop opinions of your own.

  13. Re:Not again... by Klaidas · · Score: 1

    True. And I do dual boot ubuntu too.
    But what I wanted to say was an example of an averange Joe - he walks into a computer store to buy a new PC.. And what OS does he get/request?

  14. Re:Not again... by Klaidas · · Score: 1
    Just because you never use Linux on the desktop doesn't mean
    I do. Surprise!
    It's just that about 98% of people I see on the (Linux support/talk) forums are real linux zealots. They won't use anything with closed source. They want to "kill" Ms, etc, etc. So everytime I see "Linux ready for desktop", "Linux agains MS" I write posts like that.
    You clearly have some emotional investment
    Yes, I do, because of the reasons stated above. :)
  15. compile from source by dpilot · · Score: 1

    Cue up the Gentoo jokes...

    The 'compile from source' is what I like about Gentoo. I ran Linux for quite some before moving to Gentoo, and when it came time to install those non-distro rpms, it was frequently a crap-shoot. Try the rpm, learn about a missing dependency. Grab that, learn about its missing dependency, maybe up-level from distro standard. Grab this, find out that it doesn't play well with my distro, etc. I got quite a few non-distro things installed from rpm, but there were things that didn't, and things that I had to carefully back out and replace a base version.

    By and large, Gentoo ebuilds just work, and the variety is great enough that I've had to go out-of-distro less often. Beyond that, since Gentoo is source-based, I usually don't have to go and grab some '-devel' package that isn't normally installed, in order to build out-of-distro software. Yeah, the compile time can be a pain, but the total get-arbitrary-package-running time is generally shorter.

    Plus there isn't the old 'version n+1 is out, time to reinstall/upgrade' churn. Of course there's a lower level of continual churn, but aside from recent things like gcc and glibc levels, and modular xorg, it's pretty easy.

    By an large, I only have problems with closed-source binary packages, and some stuff that isn't properly ported to amd64, yet. (Doomsday, for one)

    --
    The living have better things to do than to continue hating the dead.
    1. Re:compile from source by Bluesman · · Score: 1

      No jokes from me. I typically use FreeBSD, and the compile from source idea is just fantastic. The problem is that only Gentoo uses it, so unless every other Linux distro adopts that, the problem remains.

      What FreeBSD gets right that Gentoo really doesn't focus on is binary compatibility, such that I can download a package for a specific release of FreeBSD that's the same as if I had compiled the port with default settings. I'm sure Gentoo will get there someday.

      --
      If moderation could change anything, it would be illegal.
    2. Re:compile from source by bouma · · Score: 1

      Check out http://gentoo-wiki.com/TIP_Providing_binary_packag es.

      You can do alsorts of useful things; have a master repository for a network with the sites own USE flags, or even make a distributable binary package from the already installed app with quickpkg.

      sure beats trying to archive up a windows app dir for backup.

      Also its loosely related but i want to mention getdelta and the dtu format which makes source dls much lighter, good on a modem, or like me on an elcheapo 32/32 wimax.

      Gentoo is evolving really fast! Having gone through lfs before gentoo existed I _love_ the foundation that portage has grown from bsd, and its still evolving.

  16. Re:Not again... by RAMMS+EIN · · Score: 1

    ``Long story short: Linux on the servers, WIndows everywhere''

    Eh? Windows runs on watches, Playstations, and Powermacs these days? And as for "if you have the choice, which would you pick?" I'd say Windows on the desktop, perhaps, but nowhere else; Linux is ok anywhere (but that's only because "the Linux OS" doesn't exist: I'd like a GUI on my PDA, but not on my router).

    --
    Please correct me if I got my facts wrong.
  17. Re:The really really sad thing is . . . by Jetson · · Score: 1
    It's still much, much easier to deploy applications on Windows
    Mainly because when you distribute for Windows you know you're normally going to have administrator access to the machine and can use any registry key and installation directory you want as long as it's obfuscated enough to miss other apps through sheer luck. Of course those are all just bad assumptions and Microsoft tells you not to expect such access, but 99% of the developers seem to write with that level of access in mind. I've had numerous Windows applications fail to install on machines where I wasn't administrator. These had no device drivers or complicated security requirements -- they simply failed because the programmer wanted to write to the protected areas of the registry instead of the user nodes.

    With windows you're guaranteed binary compatibility on a majority of systems.
    Majority != All. I find it particularly odd to see sites still offering programs for download that are not Win32 applications.

    It's a huge pain to distribute binaries for every different distro
    Well, there are two solutions to this: Use the RPM format and allow the other distros to import using "alien", or else get automated build tools. You would only have to set up the tools once with the distro-specific directories, etc.
  18. Average PC User by emil10001 · · Score: 1

    While I agree that standardizing parts of the Desktop Distributions would help, and will look forward to the future avoidance of "dependancy hell", I don't agree with the assesment that the non-standardness of these Desktop Distros causes any real undue problems for normal PC users.

    An example is my roomate, I installed Suse 10.1 on his virus laden windows box, and he loves it. There have been no issues at all with it. The biggest plus with most of the desktop oriented distros that you mention, is that there is no need for the average user to install extra software, becuase everything that most of them need comes pre-installed.

    Then there are the package managers like synaptic, yum, yast, smart, etc. which take care of everything for you, and can be easier than tracking down windows software.

    So, if an average user wanted to use a linux distro as your desktop pc, I don't see where the big issue is. The fact is that the average user will run into problems with any desktop oriented operating system, say spyware and virii with windows, or dependancy hell with linux, that they will either need to figure out, or get help for.

    1. Re:Average PC User by Burz · · Score: 1

      Assume Linux and Windows marketshare was 50/50 and that your roommate had a daughter:

      His daughter wants to experiment with some simple ideas in automatically manipulating media files, and can choose her father's Windows partition or the SuSE partition on the same machine.

      (We'll ignore that that SuSE installer will change the C: partition to 'hidden' which causes the XP disk checker to freeze on bootup, a Redmond "oops". Assume the installation works.)

      Over a period of, say 3-4 years returning repeatedly to several of her different dalliances in programming.... Which OS is she likely to settle on? I say she'll tend to settle on Windows, particularly as she becomes more ambitious and career-oriented toward programming. You see... Her Linux friends couldn't even run the Linux code she sent them. That was a real downer... all that sense of accomplishment and no one to SHOW it to!

      Her Windows pals could run her programs easily. This resulted in a networked, social reinforcing of her endeavors on that platform. Whereas SuSE has no desktop platform to offer, because the other Linux distros do not include many of the same pieces. Someone told her to learn "packaging" for RPM or DEB, but that got complicated very quickly and the problems were all confusingly different depending on which Linux pal tried it. She read something about 'LSB' being a standard she could write for, but it didn't include the graphics or audio she needed.

      Oh well...

      This budding programmer will go on to write marvelous applications that will draw many users to the Windows platform. She could have stayed with "Linux" if it had nurtured her with a stable environment; if there were a reasonably modern framework she could count on, and a beginner-intermediate IDE that was promoted and supported by RedHat, Novel, etc.

      For that matter: Mac OS has none of the problems (viruses and dependency hell) that you mention. We should be asking why, and why desktop Linux isn't learning much from the quintessential modern PC.

    2. Re:Average PC User by emil10001 · · Score: 1

      Just a few points.

      First, I was talking about average PC users, you know the people that use their computers to watch movies and listen to music, do homework, balance a checkbook and enjoy the internet. Those types of things are easily handled by the Distros that you mentioned in your original post. The Mac OS does do better in terms of dependency hell and viruses, but does not do very well in terms of flexability. You can't legally run OS X on anything but mac hardware, and then if you choose to get that expensive hardware, you are stuck with a very static UI, very pretty, but it hasn't seriously changed (with some minor exceptions) since 10.1. Linux has a number of window managers and desktop environments including some new opengl desktops that rethink the desktop as a flat 2D space.

      Second, I also mentioned that I agreed with you on the need to standardize things like libraries, I think that most of us who use a linux distro on their desktop would bennefit from that.

      Third, why would there be any issue in running code from one box to another? If she and her friends were into linux, then they might also be farmiliar with source code compilation. If the code was able to run on both a windows box and a linux box, then it doesn't sound like there was anything special about it. If she was using other libraries, then i guess it would get a little stickier, but not a whole lot as there are many projects out there that are able to manage it. The number of times I install something without any problems far outweighs the number of times I run into dependancy hell.

      Finally, building RPM's are relativley straight forward, and nothing a trip to the man pages couldn't fix.

      Also, as a side note, I've never had any issues running a dual-boot setup with windows (Suse, Ubuntu, Cent OS, etc) aside from the fact that I was allowing windows to take up precious hard drive space.

    3. Re:Average PC User by Burz · · Score: 1

      First, I was talking about average PC users, you know the people that use their computers to watch movies and listen to music, do homework, balance a checkbook and enjoy the internet.

      Yes, on the surface. But there are too many influential PC users (or 'power users) who would not be drawn to the OS without titles like Photoshop, a Quicken, etc. that are polished and inspired.

      If RPMs are so great, where are the apps I can download and install in a single RPM file?

      And man pages are, of course, insufficient to address the differing lanscape that each distro presents. In some cases, the system will just blurt out which dependencies will have to be chased-down; in other cases, the system may attempt to fetch them but have some incompatible package names and numbering. Just why a 3rd-party application should carry a list ordering which parts of my OS should be installed and upgraded (even downgraded) is beyond me... keep your apps away from making decisions about my OS!

      RPM/DEB + Centralized Repository + Repository Priest == a putrefying tarbaby that promises many hours of hardship and entanglement. Its not really better than the Windows registry. It inappropriately puts my OS components on an equal footing with user-selected services and apps, erasing the usual demarcation between them. It pressures everyone who uses it to filter their whole computing experience through a centralized software database. It puts important presentation, configuration and compilation options in the hands of Repository Priests who scarcely understand most lightweight GUI apps, nevermind the larger more involved ones.

      This sort of infrastructure is appropriate for automatically updating operating systems. But it has been misapplied to cover "everything else". The result is not so much an OS or a platform, but "distributions" that have each been rolled into a large metastacized mass. Want to install a PDF viewer? Install Nautilus + its CD burner first! Bleh.

      You would have a point about Mac OS if this sub-thread were dealing with hardware drivers. The way you drag-n-drop an app to install it on a Mac has nothing to do with hardware support. It deals with the standard set of modules/APIs that app developers know are always going to be there.

      Third, why would there be any issue in running code from one box to another? If she and her friends were into linux, then they might also be farmiliar with source code compilation.

      This is a question of inexperience, which I don't begrudge. App developers are primarily concerned with the surface APIs of the platform they build on. Cumbersome requirements that pull you under the surface to re-compile and rearrange at the system-level can and does drain away precious time, energy and enthusiasm. The only sort of enthusiasm that sort of thing encourages is for systems coding, which is almost a whole other field and attracts a different sort of programmer.

      Someone with a yen for producing stimulating AV interactivity and simulated player intelligence is simply not going to get turned-on by ways to optimize data pipes and disk-buffering routines or ways to save 6MB by relying on a repository for certain libraries, or how to choose between ALSA/ESD/ARTS/OSS sound interfaces under differing circumstances... So DON'T put them in a position where they're forced to learn it! It's crap to them, and you shouldn't believe otherwise even for a second.

      Yes, Linux does spur enthusiasm for systems coding/hacking. Unfortunately, it tends to take the form of trying to impress one's peers (other system-coders) so that features taking real consumer use-cases into account are relatively rare. Not only are use-cases unknown/ignored, but the concept of making committments to end-users is avoided like the plague. And with no general ethic of committing to users through softare design, we leave users confused and techies (also somewhat confused) unwilling to do tech support outside of casual easy-come-easy-go settings.

    4. Re:Average PC User by miro+f · · Score: 1

      I imagine that the daughter would be statically linking her simple programs that she's writing and as such would not have any issue in getting it working on anyone elses linux box.

      --
      being vague is almost as cool as doing that other thing...
    5. Re:Average PC User by emil10001 · · Score: 1

      Once again "average" PC users, not power users, not gamers, just the ones that don't actually need a computer, don't really know how it works, and can't keep the viruses and spyware off. My bet is that that is the largest percentage of users in the market (market of home users, non-buisness). Many have said that the Gimp is a viable replacement for Photoshop, and Quicken does have a linux version, if I am not mistaken.

      I'm also not sure if you missed the part that I was agreeing with you on, which was that all the interdependance causes dependancy hell. This is not the fault of the RPM, or the Deb package managers, it is the programmers who decide to incorporate system libraries in their code. Now, this does a couple of things, first it shortens the development cycle as the programmers have certain bits of their code done for them in the form of those system libraries. It also makes the programs that you want smaller in hard disk space, and also the potential for a smaller footprint becasue libraries may be used by multiple programs (like the Desktop Manager for example). And while yes, it would be nice to just have everything neatly packaged with all the libraries needed, you would be wasting a lot of system rescources, and a lot of disk space doing things like that.

      Now that said, someone doing AV interactivity is probably going to be looking at those system libraries that deal with audio and video, which are used by many other multimedia applications and most of the time, those libraries are going to be very similar between people with up to date software. So, why would they need to get into learning all the drivers?

      I think that you are missinterpreting the structure of the RPM/Deb repositories and databases. A repository is where a user would go to get new programs, which is handled by a package manager and sometimes a front-end for that. The repositories themselves are links to servers different places out on the internet. The package manager will install software by grabbing packages from the repositories and fill in the requirements for you. This works especially well if you are using a well-defined set of repositoreis (Ubuntu does this well, and Freespire/Linspire looks like they are too). There is no interaction between the user and the database that keeps track of all the data, similar to the windows registry.

      As for your comment on competing projects and lack of customer focus, you are right, and wrong at the same time. Yes, there are competing projects that can detract from having a single unit more forward faster. However, at the same time, people like being able to choose between them to get the look and feel that they like. Between the different sound servers, you will probably be able to find something that allows your strange, non-standard sound card to run. Also, you can't just merge these projects, how would you do that without throwing away large parts of their different code bases? The customer focus comes into play with Suse (the official one), RHEL, Ubuntu, Linspire/Freespire and others. Several of these offer tech support, Ubuntu and Linspire/Freespire have their own repositories that are designed to do away with dependancy hell (Suse and RHEL also have these, but you can't always find everything inside their repos). Another thing is that for the commercial projects like say, VMware, a closed source commercial product, it does come in a single RPM because it doesn't need any other libraries to make it run.

      I've done some development in the RHEL environment and absolutly loved it. The company I was with was doing all their own software, and Linux had all the right tools, built in, to do some really nifty testing that you could just forget about in windows. And these boxes were up for up to a couple of years without any downtime. I know its not on the Desk, but my point is that you don't need system libraries to write software in Linux.

      With the man pages they do in fact tell you everything that you need to know to run a program, suc

    6. Re:Average PC User by Burz · · Score: 1

      Why should we ignore or seperate power users (the kind of person who would run PartitionMagic) from the rest? They are extremely influencial in getting their colleagues, family, etc. to adopt new things. Linux turns-off the power user more than any other, because they want personal control yet don't fit either the fulltime sysadmin role or the spoonfed-user role.

      Gimp is no replacement for Photoshop. Besides the poor documentation and the GUI/menu layouts determined by the internal organization of code (instead of the kinds of tasks the user may be undertaking)... there's the lack of real white balance, no CMS, 24-bit limitation, etc, etc.

      I'm also not sure if you missed the part that I was agreeing with you on, which was that all the interdependance causes dependancy hell. This is not the fault of the RPM, or the Deb package managers, it is the programmers who decide to incorporate system libraries in their code.

      I appreciate that we agree for the need of standard desktop-focused libraries. But I may not agree with your reasoning, and its interesting to discuss: Why should anyone be punished with depedency issues just because an app uses "system" libraries? And if they're "system" libraries, then why aren't they installed by default? If they can't be counted on being in the system, then don't call them "system" libraries; call them "extras" instead and don't let them interfere with system updates or app installations.

      Also, how common is it that apps that try to supply, internally, every library they need? Right down to the bare kernel? There is a balance to be struck on every platform, between being overly feature-rich and stark efficiency/simplicity lacking in versatility. Linux distros refuse to make an effort WRT that balancing act; They don't want to commit. Mac and Windows systems come with rich functionality, slowly becoming richer over time as Apple and MS take notice of what becomes popular with users and developers. If a few developers here and there don't want to use certain offerings in the platform, they can incorporate their own code in those specific cases.

      So, why do Linux people (of which I am one) tend to think that including standard functionality (a defined platform) at a med-high level translates into a situation where developers have to "include all libraries themselves". Huh? It makes no sense.

      I'm not pointing the finger solely at distro maintainers: It's the *process* that our community of elites has rallied around. We can't reasonably expect the general public to be able to use this for personal computing (thin clients, yes; PCs no).

      I'm a certified Linux admin with a programming background. I know exactly what RPM files, repositories and package dependencies are. Together they comprise a web-like centralized database of interdependant linkages, and to extend enforcement of that system amorphosly beyond the core OS into "extra" features and applications is wholly inappropriate to facilitating independant software distribution for PCs. And by your own description a curious beginner must learn and wrangle with this beast before even getting to "show and tell", although I can assure you her curiosity probably doesn't extend to repositories and package managers. Instead we are obliged to, gently or otherwise, throw "RTFM" at her.

      Which is why you won't see people like her writing compelling titles for Linux later on. Bet you can find her at MSDN or ADC though.

      Between the different sound servers, you will probably be able to find something that allows your strange, non-standard sound card to run.

      LOL! How can a Linux advocate point a finger at "non-standard" sound cards when our OS doesn't offer a standard API for audio? Why is the burden of standardizing always on someone OTHER than the Linux distro? RedHat, Novel, Canonical and all their community counterparts distribute audio software that use either AlSA or OSS /dev/dsp which is odd because the two are mutually-exclusive without using la

    7. Re:Average PC User by Burz · · Score: 1

      Oh, come on now...

      What if she writes them in Python or Ruby?

      You didn't assume I was talking about C, did you? :-)

    8. Re:Average PC User by emil10001 · · Score: 1

      Hmm... a few things, first I'm going to appologize for the comment I made about the repository thing, I missread your previous post. Second, I'm going to agree with most of what you said, because you make a lot of sense.

      The things I don't agree with are the Core Desktop thing and apps not using system wide libraries. To me the idea of merging everything and filtering it down into one unit seems like a daunting task. I think it'd be really cool if the system wide libraries were standardized and all that jazz. But, I don't think that combining the different projects will happen.

      Take Gnome and KDE for example, two projects that have similar capabilities trying to accomplish similar goals. I've used both for a good period of time before I settled on KDE. It's simply personal preference, and I'm glad I had that choice to make. I like the way KDE looks, and while I feel that Gnome can be more stable, KDE is my choice. I don't really see how these two projects (aside from just starting something from scratch) without losing the look and feel of one or the other, as to me, it seems they are both unique. This is how I feel that a lot of the competing projects are, they have their pluses and minuses, and the user ends up choosing the one they like best.

      As far as different applications bundling the libraries in with them, I have a feeling there might be some legal issues with that, but aside from that I think that the different apps would greatly increase in size. I really like trying to keep my root partion under 12GB, and I have a ton of software installed on it. That wouldn't be possible if libraries were bundled with the apps. If you used standardized system wide libraries, then the apps that use those aren't going to run into dependancy hell. I think the big issue right now is using all of the bleeding edge stuff, some developers want to use the latest libraries for their new apps, and some users want the absolute latest everything. So, you end up with a half-updated system where you have a lot of older libraries and a lot of newer libraries and then you try installing an app that wants all newer libraries, or some older and some newer, but different from what you have.

      Now, the sound server thing, again, I agree with you, I've had that same issue where the sound cuts out of one thing because another is going on. I was simply saying that while one of those projects might not support a card, another might.

    9. Re:Average PC User by emil10001 · · Score: 1

      I also forgot to metion about the average user versus a power user. I advocate moving average users over because they have an easy target for bad things: viruses, spyware, identity theft, etc. While power users can generally be expected to deal with the required security. Average users don't know the systems well enough to have much trouble using the KDE or Gnome, while the power user would have some other things they are farmiliar with. I think that the power users are somewhere in the intermediate level, and while they could figure it out it would take them time to do that which they are not willing to spend. I think those people do well with windows because they know what to do (in general) to keep themselves protected and keep their box running well. Average users would do well with something besides windows because they do not know how to keep themselves protected, and keep their box running well.

      I also wanted to mention how kick-ass man pages are, in general. Nobody should feel bad about telling somebody to RTFM because in the end they will gain more insight from the man pages then anyone's advice could give them. It was a bit daunting at first to me, but then after I got used to it, it has really helped me out. Instead of going to Google for something right away, I read the man pages first (google usually just reinforces what I already figured out).

      Again, not so much dissagreement as I'm just throwing that out there.

      ... and thanks for the interesting conversation.

    10. Re:Average PC User by Burz · · Score: 1

      The things I don't agree with are the Core Desktop thing and apps not using system wide libraries. To me the idea of merging everything and filtering it down into one unit seems like a daunting task.

      Some misunderstanding here I think: When I say 'core desktop' I mean core APIs that ISVs would use to target a broad desktop audience. For example X11, gtk+, qt, dbus, etc. I am not referring to an actual Gnome or KDE desktop.

      I dislike man pages on Linux because 1) they sometimes say 'use info instead', and 2) they almost always omit examples. BSD is much nicer for 'man' and its one of the reasons I have grown to like OS X so much in the past 18 months since I bought a Mac.

      As far as different applications bundling the libraries in with them, I have a feeling there might be some legal issues with that,

      Indeed, independant commercial developers wouldn't be able to statically link GPL stuff for starters. All the more important that devs have assurance certain libraries will already exist in the system (even better if their program only has to check which LSB level the system is at).

      A 12GB root seems very large to me. I notice my root tends to expand greatly when I've got a lot going in /usr/src. That would seem to indicate over-reliance on source code as mere distribution vehicle (as opposed to a way for a skilled user to wrest control in very specific cases) is the more disk-hungry than binary-focused distribution. On a more practical level, the capacity issue is somewhat moot. Hypothetically, an ISV offering a complex app for Linux, Mac and Windows would probably feel the most pressure to "include the kitchen sink" in the Linux version precisely because they have no assurances as to the features of the host Linux systems, whereas the Mac and Windows version can be smaller due to those environments being more predictable. I believe this even shows when you compare the sizes of apps like Firefox, Skype and OpenOffice. (Mozilla gave up on packaging Firefox for Linux, offering a plain 'drop it in /usr' binary with no dependency information; Firefox packages that we normally use come from our distros not Mozilla.)

      My theory about users (which relates to experience) is that average users will always buck you in the end if you recommend a suitable Linux system that nevertheless makes their power-user friends feel helpless. Linux has to recreate some of the Mac/PC social evolution in order to offer a true desktop alternative: The PC catered to power users first and foremost, while the Mac started with a simple-user focus and migrated toward accommodating power-users (somewhere between the hypercard and applescript days is when the Mac made this transition). Otherwise, we tend to come off as dusty and irrelevant Unix priests, seemingly unable to do half of the wizardly
      feats that power-users apparently have mastered with their mix of commercial, shareware and FOSS. We are also unable to make many tasks go 'click' in the novice's head, because what we have to show them is a lot less consistent in terms of GUI semantics (sometimes with no GUI at all). Its like being on Ubuntu and showing them Firestarter because no integrated Control Panel front end exists, and then showing them how to execute an iwconfig script in the CLI because the Control Panel supports wireless, except for certain common features like WPA. Then from there you move onto KNetworkmanager, because there's no inbuilt way to detect/switch access points easily. What a jumble.

      Perhaps you see already where I'm going with this... that eventually lightweight sysadmin duties (like enabling the firewall, or changing screen res) will have to have standardized control panel UI components in order for professionals to regard Desktop Linux as supportable. So the next question is: How are we turning-away young would-be sysadmins? Yes they will eventually need to handle /etc directly... but is it wise for LSB to leave vi as the only must-have editor, forcing inst

    11. Re:Average PC User by emil10001 · · Score: 1

      Again, I'm in agreement with most of that, I think I might have an answer to your question about leaving vi as the only "must-have" editor. There was some discussion at my old job about vi vs. emacs, and how there were always a couple of people who perferred to use emacs over vi for editing. The problem was that with emacs, you have to go and install another package that isn't in the default install. I know that your point is that there should be a couple of editors in the default install, which would follow the standard. But right now, if you hop on a *nix system, you can expect to be able to use vi. I'm not saying that there is anything better about vi, just that it is already the default and widely accepted, so why change it? I don't think that it was really all that difficult to learn, I had a book, or two, and the man pages, and I went to town. Same deal with sed, awk, grep and a host of other useful utilities. They can be cryptic, but they are also fast and get the job done. I actually had time to learn sed and awk, and write a script to do some text manipulation, in less than half the time it would have taken me to edit all that stuff by hand. So, learning those things isn't all that bad, and with the proper motivators can be quite rapid.

      Yes, that hardware compatability list would be quite nice. As it is now, I look it up on newegg, see if I can find the chipset it uses, then spend at least a half an hour googling around, trying to figure out if I'll have any problems getting it to work. It's funny that the OSx86 project wiki has such a list - which is quite useful. I learned quickly that buying cheap hardware that is incompatable ends up being more expensive than the right hardware that works, because you need to get the right hardware anyways.

      I too have wondered how to push the Linux movement beyond what it is today, and I've thought of a lot of the same things that you brought up. Most of the time, I think about all the system libraries and dependancies that programs use. And how to build a system that would not just take care of the dependancies, but allow you to install certain libraries locally so that you can have multiple versions of a library installed. Say that MPlayer wants version "A" of a library and Xine wants version "B", well since version "B" was already on the system, and has some other dependancies, it cannot be replaced by the older version "A". So, instead you could tell the installer to put version "A" in a place where only MPlayer can get to it. In other words, version "A" is local, and version "B" is system wide. And on top of that, having the package manager do all that stuff automagically, go find the missing libraries, and install the unsolvable dependancies locally. This would also fit in with the standardized desktop wanting to run apps that were built with non-standard components. Anyways, that is my solution to dependancy hell, but it still has the issues we already discussed, such as the footprint and disk usage.

    12. Re:Average PC User by Burz · · Score: 1

      Nano is very tiny, and could be added to the LSB with absolutely no trouble. Then one could say that anytime you hop onto a Linux system, you can choose nano if vi seems too arcane. From there, realizing that OS X also includes nano, it is not a stretch to say that nano would be emerging as a *nix standard. It is already used in most OS X examples as a common-sense way to do quick edits in the CLI.

      The problem with vi is that to many people it is outright repulsive. When told to use it, I infer an underlying attitude of "We don't care about making you deal with unnecessarily arcane tools and formats". Still, I'm not saying it should be abandoned or removed... its just not a program that ought to be forced onto anyone at the 'Webhosting 101' or 'Junior Linux Admin' stages.

      Sed and awk are fine the way they are, but people are not going to be expected to learn them just so they can perform rare, emergency system maintenance. With vi, its a different story.

      That is how I see it anyway. If it were up to me, I would replace 80% of /etc stuff with XML files, making sure that a good text-mode XML editor with tree/node view was included. Too many subsystems on Linux integrate poorly because their config/control options are based on their /etc file, a custom format with vague rules and/or poor documentation. The first nonsense file format to be slayed would be xorg.conf. But that's just daydreaming. :-)

      Your idea about relocating libraries for certain app dependencies reminds me of Apple appdirs: The non-standard version of the library stays in the appdir, and appropriately the vendor that supplied it with the app is responsible for how well it functions. I think that should be standard procedure when developing any app on any OS: If you insist on holding back to an older version than the OS specifies, then (if licensing allows) it is your job to include it with the app and have the app load it from its own folder. Making the rest of the system deal with your decision is just wrong, but unfortunately that's how its done on "Linux".

      The HCL idea has been burning in my mind for over a year. If I could figure out a way to attract a real following (and some hardware expertise) to it, I'd set up a project website. Probably the first thing to do would be to compile information from the various fragmented hardware lists; these would be some starting points:

      http://mradomski.wordpress.com/2006/07/09/linux-ha rdware-compatibility-lists-hcl/

      http://www.linux.org/vendor/hardware/index.html

      http://support.xandros.com/hcl.php

      And that earth-shattering question: What to call it?

  19. Re:The really really sad thing is . . . by Burz · · Score: 1

    Mainly because when you distribute for Windows you know you're normally going to have administrator access

    As usual, the existence and relative success of OS X negates such claims.

    Automatic package managers + huge repository seem nice at first. Until you realize there are Zero independant application developers offering great stuff for your OS, because the distro differences and their PMs continually massaging/tossing around system components have scared off those types of developers. Want your stuff to install and keep working on the PCs of users A, B and X? Then find out what their distros are and surrender your code so that a 'maintainer' middle-man (with probably no interest or real experience with anything more high-level than Firefox) can manage it for you. Ha. There goes control over your code. There go modes of distribution like application on a CDROM or a ZIP file. There goes the close relationships you might have formed with most users who cannot/willnot operate a compiler. All out the window.

    None of this is really an obstacle to nerdy sysadmins or those to write software targeted at them, because they have IT insight and experience. But for everyone else, such as authors/users of PC applications, its lethal.

    Mac and Windows serve as relatively stable environments, where PC developers and users meet. Or if you prefer, they "interface". That is how a PC software platform has to work. To our Linux community, this direct interfacing without a distro 'maintainer' between them is treated as 'unclean'. And if Linux distros were as carelessly written as Windows, the author/user seperation habit probably would improve cleanliness (less malware); however that is not necessarily so and it is proven untrue in the case of Mac OS X, which has the PC software model without a malware epidemic.

  20. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  21. Re:Not again... by swillden · · Score: 1

    They won't use anything with closed source.

    So what about those who use closed source apps on Linux?

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  22. Re:Not again... by Kawahee · · Score: 1
    --
    I'll subscribe to Slashdot when I see a month without a dupe, a typo, or an article the "editors" didn't read.
  23. this makes me think of ... by David+Gerard · · Score: 2, Insightful

    The Linux pride, or simply pride, campaign of the open source movement has three main premises:

            * that all people of all computing orientations should be proud, not ashamed, of being young white middle-class Linux-geek men;
            * that computing diversity is a gift to young white middle-class Linux-geek men;
            * that computing orientation and operating system type are inherent, unless of course you dual-boot Windows and FreeBSD and are therefore only fooling yourself.

    Pride Parades are held worldwide, wherein young male white middle-class Linux geeks of all colours, ages, operating system types and backgrounds can walk down the centre of the main street of their city and commemorate the original Stallmanwall printer driver riots.

    Many parades still have at least some of the original political or activist character, especially in less Linux-positive settings. However, in more Linux-positive cities, the parades take on an installfest-like character. Large parades often involve floats, coders, Mountain Dew, venture capitalists, and amplified music; but even such celebratory parades usually include political and educational contingents, such as local politicians and marching groups from open source institutions of various kinds. In some countries, Linux parades are now also called Linux Pride Install Festivals.

    Even the most festive parades usually offer some aspect dedicated to remembering victims of Stallmanwall and anti-Linux FUD. Some particularly important Linux parades are funded by governments and corporate sponsors, and promoted as major tourist attractions for the cities that host them. Other typical parade participants include local Linux-friendly churches such as Emacs Community Churches and BSD Universalist Churches, PFLAB (Parents and Friends of Linux and BSD), and the nerd employee associations from large businesses.

    Though the Stallmanwall riots themselves as well as the immediate and the ongoing political organizing that occurred following them were events that were fully participated in by BSD users, X11 people and future Sun founders as well as by white middle-class male Linux users of all races, genders and backgrounds, historically these events were first named Linux, the word at that time being used in a more generic sense to cover the entire spectrum of what is now variously called the Red Hat, SuSE or Debian community.

    By the late '80s and early '90s, as many of the actual participants had grown older, moved on to other issues or passed away, this led to misunderstandings as to who had actually participated in the Stallmanwall riots, who had actually organized the subsequent demonstrations, marches and memorials and who had been members of early activist organizations such as the Linux Liberation Front and Linux Activists Alliance.

    But eventually the language caught up with the reality of the community and the names have become more accurate and inclusive, though these changes met with initial resistance from some in their own communities who were unaware of the actual historical facts. Changing first to Linux and BSD, today most are called GNU/Linux/X11/KDE/GNOME/Mozilla/gcc (GLXKGMg) Pride Parades. But only by the sort of geeks even the other geeks don't want to hang out with.

    Remember: just because you have a personal coding output of zero doesn't mean that you can't take full credit for the programming genius of others for a lifestyle of Slashdot, caffeine and masturbation.

    And believe me, you haven't lived until you've seen twenty Linux geeks clad only in silver jockstraps.

    http://uncyclopedia.org/wiki/Linux_Pride

    --
    http://rocknerd.co.uk
  24. Desktop? by Monsuco · · Score: 2, Informative

    It seems like Linux is now becoming a major competitor to Windows and Mac on the desktop. It hac come a long way. With the advancment of binaries like .deb, .rpm, .bin, and scripts it is getting easier and easier to install things on linux. Wine has gotten so that most Windows software with exception to some games and programs that need drivers will run. I can easily run IE, WMP, Shockwave, the latest Flash, Outlook Express, Office, and the like. More and more hardware vendors have been supporting linux. The winmodem problem seems to have been solved not by the development of drivers (though that has happened) but by the spread of broadband and ethernet. WiFi support has improved. Gaim has IM covered. Firefox's spread has helped linux be able to read more web pages by discouraging IE only pages. OOo has goten good at dealing with office documents. iPods work. Flash and Java and MP3 and Real are all supported. The only real problems are legal DVD support and legal WMA and Quicktime support. There are games on linux. What is missing, we need OEMs.

  25. Microsoft library by r_jensen11 · · Score: 1
    Microsoft library:

    how about http://www.microsoft.com/products/? Sure, you can't instantly install the programs there, but neither can you if you go to www.gentoo-portage.com. Hell, even with some programs (e.g. Maya,) you still can't do "emerge maya" or click "Emerge" with Porthole, and something makes me thing that the same situation exists with Yum and Apt.

    Don't get me wrong, I love Linux and use it for my computing whenever I'm not doing things that are currently much easier to do under Windows, or things that can only be done under Windows. Hell, just two days ago I got a BSOD when all I was doing was looking at www.economist.com and ripping some movies. Speaking of BSOD's, I've been getting quite a few of them lately, and I know I don't have any viruses....

    1. Re:Microsoft library by Procyon101 · · Score: 1

      The only peice of software I've ever needed to get manually to plug into portage was the Sun JDK, as I've never used Maya. This is a very uncommon scenario.

      MS may have a website similar to gentoo-portage, but once the software is found, for every case in the MS instance, I must then go manually either download the software from the vendor or have a CD snail-mailed to me (how quaint) and this is the epitomy of the MS distribution chain. On Gentoo, for nearly every case, I simply:

      emerge --searchdesc what-am-i-trying-to-do
      emerge program-i-found
      run-program

      MS would *LOVE* to have a distribution system like this. Unfortunately, as another poster said, they can't, as they would be stepping on their customer's toes who's bread and butter is software distribution.

      Linux (and BSD) are winning hands down in the install and distribution arena.

  26. Download.com by westlake · · Score: 1
    Getting winamp or nero or whatever application you want is very easy if you know which app you need and where to get it. But show me where is the centralized application install function in XP, like Adept or Synaptic in Linux. Where is the simple way to look for a software to install, searching by category?

    Download.com. will serve as an example. I could as easily have chosen a half-dozen others.

    Programs neatly sorted in categories. Independent editorial reviews. User reviews. Screenshots. Tutorials. Licensing and prices.

    Let me know when your typical Linux disteo provides that much help for the beginner.

    You Microsoft guys have no idea how complicated is getting software for Windows if you are a newbie. You just think it's easy because you are so familiar with the whole thing

    My youngest niece began with XP at age four. Her older brothers with Win95 in 1996. The truth of it is that there are no Windows newbies.

    I may be out of date myself here, because it has been a long time since I did this, but I remember that even in 1998 automake/autorun were easier to use than solving all the incompatibility problems between windows applications and DLLs.

    I made the move from Win 95 to Win XP in one leap and in little more than one day. Programs written for Win 3, Win 9x, XP and MSDOS still coexist on my system even now.

    1. Re:Download.com by westlake · · Score: 1
      You should check out freshmeat.net

      If I am in the mood for for self-torture I can (a) search an OSTG site in the hope of finding something useful or (b) have my next root canal done without the anesthetic. I chose (b).

  27. My USB keyboard experience by quazee · · Score: 1

    I had a similar problem when I was trying out SuSE Linux 9.1 x64 a couple of years ago.
    The installation went OK, however, the keyboard never worked in GRUB, even if 'USB Legacy Support' was enabled. After some fiddling, I finally had to give up and use a PS/2 converter.

    I think the problem is somehow related to the fact that the keyboard was not just a USB HID keyboard device, but a USB Composite device, containing two USB HID descriptors (a keyboard + a mouse).
    The mouse descriptor is probably there because the keyboard has a scroll wheel, which works exactly like a mouse scroll wheel without installing any additional software.

    --
    throw new SuccessException("Sig read successfully");
  28. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  29. CameWithTheHardware.com by Anonymous Coward · · Score: 0

    "Getting winamp or nero or whatever application you want is very easy if you know which app you need and where to get it. "

    Let's see. Bought a DVD burner last week. Came with the Nero suite. Can't get any simpler than that.

    1. Re:CameWithTheHardware.com by Ash+Vince · · Score: 1

      Same for Linux. Nero has a version for Linux, its what I use for burning DVD's.

      What? You say your hardware didnt come with a disk for Linux? Did it come with a disk for OSX as well as the windows one?

      And talking about bundled software with hardware did you know that usually the software vendor pays for this so they can fob substandard software off on to users who don't know any better and will buy the full version anyway (Global DVD / WinDVD anyone?)
      This business model will only work when you have a large number of uneducated users who buy software without reading anything about it first (Or without checking that they need it)

      --
      I dont read /. to RTFA, I read /. to offend people in ignorance.
  30. But on the Linux side, there's rpms.. by twoblink · · Score: 0

    I run gentoo, so "emerge app" will do it for me. As for Debian, apt will do it also.. But not everybody in the linux world is equal.. rpm's are pretty much God's way of punishing the Linux users... My wife can install Windoze by herself, and she is very capable of downloading from download.com or tucows or somewhere else and "doube-clicking" and having the app install itself. Now, if I throw her a rpm, and put her in dependency hell, then you will quickly see that Linux was designed with the geek, and not the average user in mind.

    When all set up, she uses my Gentoo box without any problems. In fact, I've got her using Thunderbird, Firefox, and so she sometimes doesn't even remember if she's using a windoze box or a linux box.

    I prefer the GUI for some things, and the CLI for others. Each has strengths and each has weaknesses..

    The real pony everybody should be talking about is configuration..

    Usually, a unix program takes me 30 minutes to an hour to configure. Much longer than Windoze. BUT, once configured, I pretty much never touch it again. Also, because most are in the /etc and live as a flatfile, I can email it to a friend if I need help, or just make a copy to back it up. This however, is nigh impossible to do in windows most of the time. When I restore a box, I install all the apps and then copy over the old config files. All done. In windows, it takes me 4234 mouse clicks to try to reconfigure things the way I had them before.

    What I can't imagine is deploying 1000 boxes using a gui.. Clicking next next next until my finger falls off is not my idea of network administration. "Oh Windows has a CLI!!" Right, and I read the Victoria's Secret catalog because I actually care about Fall Fashion...

    The problem is most Windoze people aren't honest with themselves. Windows is great for some tasks. But for others it bombs. Linux is great for some tasks, but for some, it bombs as well.. People just need to be honest with themselves..

  31. Next slashdot article by crossmr · · Score: 1

    http://www.google.ca/search?hl=en&q=zomg+internet! &btnG=Google+Search&meta=

    Its really that easy to make your own article to submit to slashdot.

  32. Downright true: where are the OEMs? by wild_berry · · Score: 1

    This issue needs the attention of distribution teams. Bug #1 on Ubuntu's bug-tracker indicates their issue with Microsoft's dominance; Mark Shuttleworth should be sending delegates to OEMs to have a live Ubuntu experience included on the computer. The possibility of giving OEM's an edition of Ubuntu to be usd as the restore software for a broken Windows install (with the option of living with the Ubuntu recovery desktop or installing a fresh Ubuntu instance instead of recovering Windows) would be a good start on the road to OEM inclusion, which is where the Desktop Linux presence has to begin.

  33. Using vi in a console.... by Joce640k · · Score: 2, Funny
    Yes, Linux can usually be fixed, but if the "fix" involves running vi in a console then it's not really an option for Joe Public.


    This issue *is* common, it's the real reason Linux isn't making big inroads and it doesn't look like it's going to be fixed anytime soon.


    User: "How do I get Quake 3 to run in Linux?"

    Zealot: "Oh that's easy! If you have Redhat, you have to download quake_3_rh_8_i686_010203_glibc.bin, then do chmod +x on the file. Then you have to su to root, make sure you type export LD_ASSUME_KERNEL=2.2.5 but ONLY if you have that latest libc6 installed. If you don't, don't set that environment variable or the installer will dump core. Before you run the installer, make sure you have the GL drivers for X installed. Get them at [some obscure web address], chmod +x the binary, then run it, but make sure you have at least 10MB free in /tmp or the installer will dump core. After the installer is done, edit /etc/X11/XF86Config and add a section called "GL" and put "driver nv" in it. Make sure you have the latest version of X and Linux kernel 2.6 or else X will segfault when you start. OK, run the Quake 3 installer and make sure you set the proper group and setuid permissions on quake3.bin. If you want sound, look here [link to another obscure web site], which is a short HOWTO on how to get sound in Quake 3. That's all there is to it!"


    User: "How do I get Quake 3 to run in Windows?"

    Zealot: "Oh God, I had to install Quake 3 in Windoze for some lamer friend of mine! God, what a fucking mess! I put in the CD and it took about 3 minutes to copy everything, and then I had to reboot the fucking computer! Jesus Christ! What a retarded operating system!"

    --
    No sig today...
    1. Re:Using vi in a console.... by ElleyKitten · · Score: 1

      Oh my God, can we please stop repeating this false, outdated "example". With Ubuntu (and many other distros) 90% of the programs that anyone needs are in the repositories, and installing from a repository is much easier than installing in Windows. Quake 3 doesn't happen to be in Ubuntu's repositories, but installing it doesn't have to be nearly as complicated as you make it sound.
      Step One: wine /media/cdrom/setup.exe (oh horrors! the command line! well, quake 2 is in the repositories if you're that scared.)
      Step Two: Follow Windows directions.

      --
      "What is Internet Explorer 7? Are you saying we can't access the normal internet?" - I love tech support. Really.
    2. Re:Using vi in a console.... by lachlan76 · · Score: 1

      Even easier actually. All you have to do is run the point update and copy the pk3s off of the disc.

    3. Re:Using vi in a console.... by kimvette · · Score: 1
      Yes, Linux can usually be fixed, but if the "fix" involves running vi in a console then it's not really an option for Joe Public.


      I agree with that. This is why editors such as pico, nano, etc. exist and is why howtos for novices should reference "how do I edit files" and cover those user-friendly editors.
      --
      The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
    4. Re:Using vi in a console.... by Laur · · Score: 1
      Yes, Linux can usually be fixed, but if the "fix" involves running vi in a console then it's not really an option for Joe Public.

      Are you suggesting that regedit is somehow okay, but using a text editor (it doesn't even have to be vi) is not?

      --
      When you lose something irreplaceable, you don't mourn for the thing you lost, you mourn for yourself. - Harpo Marx
  34. Repeat: Linux is NOT Windows by boyfaceddog · · Score: 1

    Linux is not and will never be Windows. Windows is a consumer grade toaster-OS You can't really change anything and that's the way consumers want it. linux is a developer grade erectorset-OS. Change it any way you want. Flexibility frightens the consumer. They want everyone to have the same OS as they have themselves so they can feel as if they fit in. Linux is for people who don't need to fit in.

    --
    Here will be an old abusing of God's patience and the king's English.
  35. The warm and fuzzy factor, THE whole point. by sco_robinso · · Score: 1

    People dont want to care about package X not working with distribution Y. People want to know or care about dependancies. People want to double click or insert the CD and the program installs. People dont want to compile anything. Compiling things scares people. No matter how 'easy' the command (line) might be, the very fact it's a command is already too much for most people. People dont care about what program they're using is installing packages or rpms. Folders named /bin /etc /home /usr scare people. The warm and fuzzy names of 'My Computer' and 'Documents and Settings' dont scare people. Being able to SSH in to your terminal is not something people care about. People want thier warm and fuzzy GUI when they log in remotely. All of these things which linux is admittedly very good at and very flexible, the average person doesn't want to even know about.

    It's been argued here at length an infinite amount of times, but the very things that Linux is good at is also what holds it back from mainstream adoption (or at least slows it down a great deal). The power and flexibility that linux offers will always far surpass anything that Microsoft can throw at the OSS community. However, people here are missing the bigger point. Microsoft succeeds (for an number of reasons, but) because what they do is warm and fuzzy, and familiar. Im a linux advocate, but I;m not going to kid myself and start to think "Hey, maybe the command line IS something that the average person should use" .

    All Im saying is alot of you I think are missing the point. Until Linux gets a whole lot more warm and fuzzy, it wont be stepping on MS's toes too much in the home-user sphere.

  36. Multilingual Support in Linux vs XP by circleback · · Score: 1

    I first must say that using Linux maybe not quite as easy as XP but, its pretty close. It just takes a bit of learning, maybe slightly more time than learning XP however. Multilingual support in XP stinks... If you want an English system plus a Chinese system for example... its just not possible. In Linux however, I have my account in English, but I have set it up where my girlfriend (who is Taiwanese) can log in and everything is in Chinese. All the menus, help docs.... everything! On top of that setting up Chinese input is a breezeat least in SuSE). The same applies to other languages as well. I just set up a French version for a friend of mine. Again, both in English and French. Thats very forward thinking!

  37. We need BOTH. by Zulkarnain+TT075910 · · Score: 1

    for personal use and comercial use .....we human being need both of it...because both of them got pros and cons. For designer we need ADOBE...and we cant live without it. For aggresive user, linux is the best choices. Security wise, free license, upgradebility and customization are excellent reason why expertise field using linux. Dumb user just go on with the windows unless you want to learn something deeper. It is good if one of them can stack each other...either windows with linux or linux with windows. It seems revolution is needed for greater invention of course we're happy with it. Linux is great when user are used to it ( take some times ) but when the fussy problem came your head will be mess. Why windows are easy to use?...because you pay A LOT OF MONEY TO microsoft so they have to provide easier and effective for their client...what you pay is what you got. Im happy if both of this OS can integrate and stack together, for dumb and expert user there is only one choice!..we shouldn't debate and compare which one is the greatest.

  38. _you_ don't have a clue what you're talking about by mohjlir · · Score: 1

    Where is the simple way to look for a software to install, searching by category?

    Hey, they've got that for windows now!