Slashdot Mirror


Ask Slashdot: What Video Games Keep You From Using Linux?

skade88 writes "Everyone knows content is king. Many of us use Windows or OS X at home instead of Linux because the games we love just are not available on Linux. With Steam moving forward for a Linux launch, I would like to hear from the Slashdot community on this topic. What are the game(s) you cannot live without? If they were available in Linux would you be happy to run Linux instead of Windows or OS X?"

5 of 951 comments (clear)

  1. Pretty much all of them by MrEricSir · · Score: 5, Insightful

    Aside from a couple of great indie games, the majority of the games I've enjoyed in the past few months are not available for Linux.

    The opposite question would have a much shorter answer.

    --
    There's no -1 for "I don't get it."
  2. Re:This is a loaded question by DarksideCoatiMundi · · Score: 5, Insightful

    Half Life 3. If that came out on just Linux I would switch to Linux and never look back. And if they brought a new release of Alpha Centauri to it too, the honey pot would just grow that much sweeter.

  3. Re:Shall I list the reasons again? by Mad+Merlin · · Score: 5, Insightful

    Drivers, installed base, drivers, familiar windows interface, drivers, most users can barely power their machine on much less install linux, drivers, forget installing linux software...see comment before the last comment, drivers, lack of vendor support, and drivers.

    Oh did I mention drivers?

    You play weird video games. Personally, I like playing the "my computer works already, I didn't have to hunt down twenty drivers from twenty different sites and make sure I kept them all up to date individually" game, that's why I already use Linux (and have for nearly a decade).

  4. Re:Microsoft Office by lorinc · · Score: 5, Insightful

    Then what format should one use for "important documents" that are intended to be editable?

    (La)TeX

    This should not be moded funny but insightful. If you ever work in the scientific academic domain, every important document is formatted in Latex, and they are all still editable whatever the bazillion versions of Office came in between.

  5. Re:This is a loaded question by bertok · · Score: 5, Insightful

    Not only does my Linux installation boot in under 30 seconds (SSD drives are great for that)

    So, you compare Linux on an SSD to Windows on a mechanical drive -- seriously?

    I should have just voted you down for spouting something so stupid, but you touched on something interesting without realizing it:

    Most of the programs I use in Linux have functional Windows equivalents, but using Windows feels like trying to run in a dream.

    This is more meaningful, but not for the reason you think.

    Your problem, like all Linux users who try Windows, is that you don't follow the rule that "When in Rome, do as the Romans do".

    Almost certainly, you tried some replica of your Linux toolchain: Cygwin, Bash, Perl, Python, PHP, or whatever, and you were "not surprised" that "Windows was slow" running software... designed for Linux. Meanwhile, Windows runs just fine running software designed for its architecture, but you probably never gave any of that a serious try. Visual Studio starts in a fraction of a second for me, complies practically instantly, and I've seen IIS put out 1100 dynamic web pages per second on my laptop, so I don't think it's all that slow. I've heard people complain that MS Word is "bloated", but it takes 200ms of CPU time to start. Bloated? I think not.

    There are many subtle architectural reasons for this. Things like: "new process" is cheap on Linux, and used for what most programmers would call "threading", but on Windows it is a heavyweight activity that's not intended to be fast. Instead, "new thread" is the fast operation. Software has to be written to start few processes and many threads to perform well on Windows. It's only very recently that Linux got good support for high performance threads, so practically no Linux software is written like this. Every damned thing starts a new process for everything. Linux scripts treat "new process" as if it was lightweight enough to replace "call procedure". Meanwhile, Windows PowerShell starts a single process which calls functions directly from dynamically linked DLLs. That's because it's designed for Windows, unlike Bash.

    Please, just shut up, and try Windows 7 x64 on a real machine with an SSD, run software on it designed for it, and only then come back and tell me that's it is slow.