Slashdot Mirror


DX11 Coming To Linux (But Not XP)

gr8_phk writes "As reported over at Phoronix, the Direct X 11 API now has an open source implementation on top of Gallium3d which should ease porting of games to Linux with or without Wine. While still in its infancy, you can see where this is heading. All this while Microsoft hasn't offered DX11 for their own aging WindowsXP. Could it be that Linux may soon support this Microsoft API better than Microsoft itself?"

62 of 370 comments (clear)

  1. At Long Last by TitusC3v5 · · Score: 4, Funny

    Microsoft has finally give us some cheese for our wine is not an emulator is not an emulator is not an emulator is not ...

    --
    And the masses cried out, "09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0!"
    1. Re:At Long Last by skine · · Score: 2, Interesting

      Because "corn" means a large grain.

      Such as peppercorns, barleycorns, maize corns or (such as in the naming of corned beef), salt corns.

  2. Response to rampant speculation by Tetsujin · · Score: 4, Funny

    "Could it be that Linux may soon support this Microsoft API better than Microsoft itself?"

    Yes. It seems very likely to me that an open-source implementation of a Microsoft API, and implementation "in its infancy", will soon surpass Microsoft's own offering.

    I mean, if you're comparing DX11 support on Linux to DX11 support on XP - well, some support is better than none, right? So, OK, sure.

    --
    Bow-ties are cool.
    1. Re:Response to rampant speculation by ifiwereasculptor · · Score: 5, Insightful

      "Could it be that Linux may soon support this Microsoft API better than Microsoft itself?" Actually Linux could soon support Microsoft's latest API better than XP. That's possible. But not better than Microsoft. That's like saying Linux has always supported DX9 better than Microsoft itself because it wasn't present in Windows 3.1 (and neither in 3.11).

    2. Re:Response to rampant speculation by Fulg · · Score: 4, Insightful

      Yes. It seems very likely to me that an open-source implementation of a Microsoft API, and implementation "in its infancy", will soon surpass Microsoft's own offering.

      I was about to post the same thing. The summary is amazingly hasty in its conclusion... I mean, WINE has been at it for what, 10 years? They still don't have it working as well as the original. Not dissing WINE, but I mean, implementing the entry points of a published API is easy. Making it do the correct things under the hood is the hard part...

      That being said, I can certainly applaud the effort, but this should be news once it's working otherwise it's meaningless.

      --
      gcc: no input sig
    3. Re:Response to rampant speculation by armanox · · Score: 4, Insightful

      I'd say WINE has done quite nicely. Remember when WINE emulated Win 3.11? WINE's biggest problem is that it will forever be playing catch up.

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    4. Re:Response to rampant speculation by Gadget_Guy · · Score: 3, Insightful

      I had a quick look at the system requirements for this project, and it said: "The following are required for DRI-based hardware acceleration with Mesa...Linux 2.6.28." This version was released nearly two years after Vista. I don't think that it can be said to support DirectX better than Microsoft when it can't run on a version that dates back to XP days.

      Now I think that it is great that they are doing this project, but saying it supports the API better than Microsoft only distracts from the developer's achievements.

    5. Re:Response to rampant speculation by JesseMcDonald · · Score: 3, Insightful

      I don't think that it can be said to support DirectX better than Microsoft when it can't run on a version that dates back to XP days.

      Irrelevant. The latest Linux kernel is available for free, and can be upgraded without any compatibility issues or changes to the UI. Why would this project waste time redoing all the work which has already gone into kernel development? The odds that anyone would be interested in DX11 on Linux and simultaneously have a good reason not to upgrade their kernel are rather slim.

      Not to mention that the whole kernel is open-source, so if you really wanted to make it work you could probably backport the necessary DRI changes to an older kernel.

      There are good reasons for retaining XP on existing systems, not least of which are the facts that upgrading would cost several hundred dollars and force a major change in the user interface. You can't upgrade an XP system to a Vista or Windows 7 kernel with DX11 support while leaving the rest of the system intact. The situations are not comparable.

      --
      "The state is that great fiction by which everyone tries to live at the expense of everyone else." - Bastiat
    6. Re:Response to rampant speculation by TheRaven64 · · Score: 4, Insightful

      You must have a poor memory then. WINE implemented the Win16 API before they started on Win32. There was a time in the late '90s when you were more likely to get a Win16 app working on Linux than on Windows NT 4.

      --
      I am TheRaven on Soylent News
    7. Re:Response to rampant speculation by rgviza · · Score: 3, Insightful

      Not really. MS won't support it on XP because they are trying to get gamers to buy Windows 7ista. I'm sure the Windows 7 support for DX11 will be on par with the linux support.

      *note I'm not a windows fanboi, I just happen to have a firm grasp of reality. I do game on windows, but my development work is entirely FOSS based on linux systems.

      --
      Don't kid yourself. It's the size of the regexp AND how you use it that counts.
    8. Re:Response to rampant speculation by oh_my_080980980 · · Score: 3, Informative

      Oh dear god you trolls. The point about the comment is that DX11 is not supported on Windows XP. Microsoft has no intention of supporting DX11 on XP and they want to kill XP. Thing is a lot of users still use XP.

    9. Re:Response to rampant speculation by The+Mgt · · Score: 2, Interesting

      MS won't support it on XP because they are trying to get gamers to buy Windows 7ista.

      Doesn't work though. Look at how many Windows games are written for the Xbox360 and are therefore run fine with Directx9.

    10. Re:Response to rampant speculation by kikito · · Score: 3, Informative

      I'd like to point out that comparing linux with Home Premium isn't fair either.

      Linux only comes in one version: Awesome.

      You should compare it with the Win7 Awesome version, whatever it's called.

    11. Re:Response to rampant speculation by paedobear · · Score: 2, Insightful

      Windows 3.1 is still supported by MS (admittedly in certain embedded sitations rather than as a Desktop OS...)

    12. Re:Response to rampant speculation by darthdavid · · Score: 2, Informative

      Honestly, stop dicking around and just use gparted or something.

  3. Does this smack of a hidden agenda to you? by mark-t · · Score: 4, Interesting

    Because I can't help but think that this may be some sort of scheme to put OpenGL out of the picture....

    I'm generally not one to presume conspiracy right off the bat, but there's something about this that just doesn't quite seem on the up-and-up, IMO.

    1. Re:Does this smack of a hidden agenda to you? by Beelzebud · · Score: 4, Interesting

      Except this isn't being done my MS. Like it or not, modern game companies are using Direct X more and more. OpenGL is already out of the picture, for the most part. With people like John Carmack now even coding in Direct X, it makes sense to try to get a solution for Linux.

    2. Re:Does this smack of a hidden agenda to you? by ChienAndalu · · Score: 5, Informative

      This is what the developer wrote in the commit message:

      Thanks to a very clean and well-though design done from scratch,
      the Direct3D 10/11 APIs are vastly better than OpenGL and can be
      supported with orders of magnitude less code and development time,
      as you can see by comparing the lines of code of this commit and
      those in the existing Mesa OpenGL implementation.

      As somebody who only has little OpenGL coding experience I can't really comment on this.

    3. Re:Does this smack of a hidden agenda to you? by mewsenews · · Score: 4, Interesting

      OpenGL is already out of the picture, for the most part.

      OTOH, Macs run OpenGL and are stereotyped as having an affluent user base. Blizzard still releases Mac versions of games. Steam for Mac launched in May. Not really "out of the picture" yet.

    4. Re:Does this smack of a hidden agenda to you? by EyelessFade · · Score: 4, Informative

      And all who make games for Consoles. Remember only Xbox uses DirectX, all the other uses OpenGL or a derivate from it.

    5. Re:Does this smack of a hidden agenda to you? by Anonymous Coward · · Score: 2, Interesting

      I only have a little GL experience myself, but I can tell you that the DX10 API is *vastly* better. Basically it takes all the OO pieces of GL like which is what modern GL code uses anyway (VBO's, FBO's etc) and throws out the requirement for you to have to deal with the very non-OO GL state machine. It's like the difference between C and Forth in that you no longer have to manage the stack of states yourself. Architecturally speaking, OpenGL's shaders are kind of weak (it basically requires the GLSL compiler as part of the driver) but in real-world terms it's pretty much a wash.

      That said, OpenGL has a far superior extension system where DX has bupkus, which lets OpenGL keep pace and sometimes set the pace. Someone seems to have lit a fire under Kronos, because OpenGL is iterating very fast (I'd even say too fast!) these days. But in API terms, it's still way behind.

    6. Re:Does this smack of a hidden agenda to you? by Bobakitoo · · Score: 2, Interesting

      In the Wine layer, Direct3D is only a warper to user-space opengl. This will allow Direct3D call, from Wine or otherwise, to talk in the most direct manner to the hardware. I doubt anyone will use Direct3D natively on Linux, except for the Wine developpers. Which already got all the missing DirectX parts that make Direct3D useful...

    7. Re:Does this smack of a hidden agenda to you? by fnj · · Score: 4, Interesting

      As the developer claimed:

      the Direct3D 10/11 APIs are vastly better than OpenGL and can be supported with orders of magnitude less code and development time

      I call BULL SHIT. I call it loudly and I call it with a big raspberry. Because: OH REALLY??? ONE HUNDRED or more times more code and development time? Thats what "orders of magnitude" with an "s" means.

    8. Re:Does this smack of a hidden agenda to you? by Anonymous Coward · · Score: 4, Interesting

      DirectX 10+ is vastly superior to what is available on Linux for writing apps,

      1. Direct3D - OpenGL is OK. It's not the largest problem after all!

      2. DirectInput - what is the Linux analogy? Using X.Org shitty API? It's akin to using Windows' WM_KEYPRESS and similar messages to do keyboard interface, except it's even more cryptic. X.Org is OK for desktop apps, like Win32 API is OK for desktop apps, but that's about it.

      3. DirectSound - let's not even get started on the horrendous crap ALSA has become. It's a prime example of *over-engineered*, unusable project. Hell, even my headset returns multiple interfaces while in fact it is 2 channels OUT, 1 channel IN. Yet in Alsa it has a shit ton of options that are completely useless, like emulating 7.1 input. WTF??

      Here's more proof how crap ALSA is,
            http://www.alsa-project.org/alsa-doc/alsa-lib/index.html

      Even the documentation is a mess. Click on high level control interface and you get a blank page!
          http://www.alsa-project.org/alsa-doc/alsa-lib/hcontrol.html

      Going from a different path (modules => high level interface), thus ignoring the main navigation page gets me a page with NO overview, *nothing*.
          http://www.alsa-project.org/alsa-doc/alsa-lib/group___h_control.html

      ALSA is one of many OSS projects that makes me ashamed of OSS. You look at projects like PostgreSQL that has *clear* and *concise* documentation available,
            http://www.postgresql.org/docs/9.0/static/index.html
      to something like ALSA, and you want to cry. ALSA looks like overengineered project by a 20 year old that simply ignored making any documentation. Winsauce!

      DirectX is NOT only about graphics. It's too bad that Linux/XOrg tends to be barely about graphics and almost nothing about the rest.

      And I'm speaking as someone that uses Linux 100% of the time.

    9. Re:Does this smack of a hidden agenda to you? by PhrostyMcByte · · Score: 4, Informative

      What he says is a criticism of what happened with OpenGL 3. Despite hopes that the old fixed-function API would all be removed in favor of the modern programmable API, it was all left in--along with the *massive* API and all the extra state and complex code it took to implement it. The Direct3D 10 API was, functionally, what most developers were hoping OpenGL 3 would be--a clean break. Smaller, optimized, easy to use, and easy to implement. OpenGL 3.1 eventually removed all the old fixed-function APIs, and OpenGL 3.2 brought rough feature parity with Direct3D 10.

      Unfortunately, OpenGL was so backwards- and forwards-compatible with itself that many games were made using some mix of the old and new functionality, so even modern games can be found that won't work without an implementation that supports the older stuff. Direct3D is a pretty rigid API without extensions, and Direct3D 10 was not backwards-compatible at all, so code that is written for it is unable to be anything but simple to implement.

      From an implementer's perspective, supporting modern OpenGL use can be a much larger problem than supporting modern Direct3D use. Of course, many games also use older Direct3D versions, and that API is bound to be much more complex too--something he didn't mention.

    10. Re:Does this smack of a hidden agenda to you? by brainnolo · · Score: 4, Informative

      What about SDL? They seem to handle those aspects pretty well

    11. Re:Does this smack of a hidden agenda to you? by TheRaven64 · · Score: 5, Informative

      Gallium drivers are in several layers. The majority of a modern GPU is basically a general-purpose processor optimised for running floating-point heavy, branch-light, programs in parallel. The back end of a gallium driver is just a compiler and runtime that takes TGIR programs and runs them on the GPU (or the CPU if the GPU can't handle them). The front end of the driver generates TGIR programs.

      Because modern GPUs are so flexible, Direct3D 11 and OpenGL 3 are basically APIs for launching shader programs, which do the real work. The front end of the driver compiles GLSL or HLSL programs to TGIR and passes them to the back end. The back end then compiles them for the native architecture and runs them.

      When you use OpenGL 2 or DirectX 9 on Gallium, you have something like Mesa that implements the older, less-flexible (but simpler-to-use) APIs by generating fairly static TGIR programs.

      --
      I am TheRaven on Soylent News
    12. Re:Does this smack of a hidden agenda to you? by retchdog · · Score: 3, Funny

      Base 1.01 - when you need to make drastic improvements fast.

      --
      "They were pure niggers." – Noam Chomsky
    13. Re:Does this smack of a hidden agenda to you? by tepples · · Score: 3, Informative

      the Wii uses Nintendo's in-house graphics API, not OpenGL.

      If the Wii graphics API (GX) is anything like the DS graphics API (also called GX), it's OpenGL with the serial numbers filed off.

    14. Re:Does this smack of a hidden agenda to you? by TheRaven64 · · Score: 2, Informative

      Sounds about right. Direct3D uses COM interfaces. This means that each version require an entirely new interface. All of the new stuff is in a separate function pointer table (COM object) and all of the new stuff is in the old one. OpenGL, in contrast, uses C functions, and new versions just add new ones (although with 3.x they've started deprecating / removing them).

      This means that the DirectX 11 API can be very clean, however the DirectX11 library also includes the DirectX 1 to 10 interfaces. Implementing DirectX 11 is probably an order of magnitude or two easier than implementing OpenGL 3.0 or 3.1, but implementing DirectX 1 to 11 is probably about as hard. If you only want to support the new APIs, then it's easy. OpenGL ES 2.0 is probably about as complicated.

      The latest versions of both APIs dispense with all of the old fixed-function stuff. In slightly earlier versions, the driver was responsible for basically providing a complete software emulator for an old fixed-function card that ran on newer completely programmable ones.

      --
      I am TheRaven on Soylent News
    15. Re:Does this smack of a hidden agenda to you? by TheRaven64 · · Score: 2, Insightful

      Not sure why you'd compare DirectSound to ALSA. The direct analogue is OpenAL, which works on *NIX, Windows, and OS X. ALSA is a Linux-specific abomination driven by the NIH mentality prevalent among Linux kernel devs.

      --
      I am TheRaven on Soylent News
  4. Support MS APIs better than MS? by Anonymous Coward · · Score: 2, Insightful

    You mean like CIFS as supported by SAMBA...

  5. Sound API is the issue now by Anonymous Coward · · Score: 2, Interesting

    Graphics are an issue but Sound is the item holding back games for Linux.

    If this can include a universal sound API then Microsoft will be in trouble.

  6. Seems sensible enough by Anonymous Coward · · Score: 5, Informative

    D3D 10/11 are pure shaders, the API does little more than compile, upload, and bind data to those shaders.

    So the only 'trick' is to automatically convert HLSL to GLSL, which again, is pretty straightforward, since concepts and structures should pretty much map up 1:1.

    Oh, BTW.. It's not DX11 it's D3D11, DirectX is no longer versioned or packaged as one big 'thing', each component carries it's own version number and release schedule.

  7. Pimp my linux. by Anonymous Coward · · Score: 5, Funny

    Hello sir, I have been told that you enjoy compatibility. I took the liberty of installing a Direct X compatibility layer on top of your WINE compatibility layer. Now you can have a compatible user experience while having a compatible graphical experience.

    Wait, did I do that right?

  8. Interesting. by Beelzebud · · Score: 4, Insightful

    I'd love this, if it's true, and it performs on par with windows. However, I've learned to take Phoronix hype with a grain of salt. They're gaining reputation for making bold claims based on no facts.

    1. Re:Interesting. by Beelzebud · · Score: 2, Insightful

      Except it's not a bold claim at all, to anyone that has read Phoronix for any amount of time. How's that Linux version of Steam coming along?

  9. great idea by ILuvRamen · · Score: 2, Interesting

    If they seriously release some really nice games for Linux that use it, people will be all over this at least as a dual boot system. Gamers love it when they do something that takes their current hardware and makes it way faster without spending any money. Judging by how fast Ubuntu ran on a Pentium 3 I had, I'd say Linux frees up a little ram for gaming. I always thought they'd take off as a gaming platform if they really pushed it because it's free and fast which is always a plus for gaming.

    --
    Google's Super Secret Search Algorithm: SELECT @search_results FROM internet WHERE @search_results = 'good'
    1. Re:great idea by Beelzebud · · Score: 2, Insightful

      RAM is still extremely relevant, it's just that a lot of PC's sold nowadays come with plenty. RAM becomes relevant when you don't have enough. :)

  10. Re:Phoronix by Anonymous Coward · · Score: 2, Funny

    100-x where x is the number of linux steam installations

  11. In ten years by Citizen+of+Earth · · Score: 4, Funny

    In ten years, Linux will be a better Windows than Windows.

    1. Re:In ten years by psbrogna · · Score: 3, Funny

      Which is convenient because in ten years that might be the minimum power plant required to support a PC running the latest MS O/S.

    2. Re:In ten years by dbIII · · Score: 2, Informative

      Had that fifteen years ago when Win95 was a disappointment, and at least twelve years ago when the Enlightenment window manager had Win7 style window thumbnail pics in the icon box.

  12. An insider view by DMiax · · Score: 5, Informative

    Disregarding for a moment the fact that this was announced a few months ago, here is an explanation of what this actually means for developers from a developer of Gallium3D. It explains why there will be no flood of games ported from Windows, and why we should still support a truly open API like OpenGL.

  13. "not XP" by airfoobar · · Score: 2, Insightful

    I thought Gallium was mostly cross-platform, so it may be possible to port DX10/11 to XP.

    1. Re:"not XP" by MostAwesomeDude · · Score: 2, Informative

      Gallium requires some sort of adapter to interface with hardware. There are no such adapters for any MS kernel, save for the closed-source VMWare stuff.

      --
      ~ C.
    2. Re:"not XP" by airfoobar · · Score: 2, Interesting

      If you are describing what I think you are describing, then they may not be too difficult to write. If you consider the market share that XP still has, it would be a very worthwhile project.

  14. 2011 is the year of the Linux desktop by electron+sponge · · Score: 2, Funny

    nt

  15. That damn Linux is at it again... by Picass0 · · Score: 2, Insightful

    ... taking an established technology - embracing, extending, and finally engulfing, and uh... wait a sec. Wha?

  16. Don't get too carried away... by joelholdsworth · · Score: 2, Informative

    ...this probably won't help Wine much. As this post explains http://www.winehq.org/pipermail/wine-devel/2010-September/086885.html : "IIRC, it's been discussed before, and it simply wouldn't work. D3D has too many ties to the Windows API that a non-Windows based implementation wouldn't be appropriate for Wine (try getting an HDC from a D3D resource, or passing an HWND to D3D). Gallium would have to substitute these for X11 resources, or custom resources that tie into X, so wouldn't reflect the Wine's internal state. Additionally, not all drivers will support Gallium (eg. nVidia binaries), so a D3D10->GL path will still be needed."

  17. Nothing to see here.. move along by kazade84 · · Score: 4, Informative

    This isn't really that exciting. Firstly it doesn't benefit Wine at all. Wine supports other platforms than Linux and other drivers than Gallium3D and Mesa and so this is useless to them, if that isn't enough the Wine source structure isn't built for this kind of swap out, specifically because Wine limits X interaction to a single DLL, winex11, and the WineD3D stuff doesn't have direct access to X. The Wine D3D developers have long said that a D3D state tracker won't help them.

    Secondly, it's not gonna help porting games to Linux either. D3D is only one part of the DX API and a game does a lot more than just draw stuff. Arguably swapping out D3D for OGL is relatively straightforward in comparison to swapping out sound API, file IO API, network IO API, message handling, etc. etc. that's why some games allow you to switch between the graphics API.

  18. With Gallium 3D? by Beelzebud · · Score: 2, Interesting

    How could Gallium 3D run Direct X 11 in any way that could be comparable to the native Windows client, when it doesn't even do basic 3d acceleration as good as the proprietary blobs?

  19. OpenGL not just used on PCs by zooblethorpe · · Score: 4, Informative

    It bears noting that various flavors of OpenGL are used on other hardware, such as Sony's various consoles or the Wii, and it is apparently part of the underlying codebase for the upcoming Nintendo 3DS system. So it looks unlikely to die in the near term, at least.

    Cheers,

    --
    "What in the name of Fats Waller is that?"
    "A four-foot prune."
  20. Re:Phoronix by MrHanky · · Score: 2, Informative

    $cd tmp/mesa
    $ git pull
    $ ls src/gallium/state_trackers/d3d1x/
    d3d1xshader docs dxgid3d11 gd3d1x Makefile.inc tools
    d3d1xstutil dxgi gd3d10 gd3dapi mstools w32api
    d3dapi dxgid3d10 gd3d11 Makefile progs

    Only about 11%, it seems.

  21. OEM vs. retail pricing; pro vs. home by tepples · · Score: 2, Informative

    Windows 7 Home Premium is only $99 from Newegg.

    As I understand it, that's the price of the OEM version, and the OEM version is available only when purchased on the same invoice as a motherboard. Otherwise, you have to buy the retail version, which is $100 more. Besides, a lot of people who need features found only in the Professional edition don't want to have to dual boot Windows XP Professional and Windows 7 Home Premium.

    1. Re:OEM vs. retail pricing; pro vs. home by MBGMorden · · Score: 3, Interesting

      The OEM version is available with any hardware purchase. My understanding is that to meet the requirement when ordering just the software they'll throw in a tiny "hardware" component (usually a screw or a cable) to legitimize it. If you have ANY other piece of hardware in your order though then even that is not needed.

      In regard to features, you have a point there, though several features that were limited to the "Professional" version of XP (such as SMP support) have migrated to the "Home" version of Windows 7. That's assuming they were even using XP Pro. I know a lot of people that were using XP Home just fine. And if you really do need Professional, then the OEM Windows 7 Pro is only $40 more than Home Premium.

      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    2. Re:OEM vs. retail pricing; pro vs. home by h4rr4r · · Score: 2, Informative

      OEM versions are only for new machines that will be resold. You cannot build your own machine this way.

      http://www.microsoft.com/oem/en/licensing/sblicensing/pages/licensing_for_hobbyists.aspx

      OEM System Builder Software
      Must be preinstalled on a PC and sold to another unrelated party.

  22. Re:Gre by Frosty+Piss · · Score: 2, Insightful

    Not really. Microsoft has made it clear that support for XP is coming to a close.

    --
    If you want news from today, you have to come back tomorrow.
  23. XP? Forget XP! by Steeltoe · · Score: 3, Funny

    I was die-hard on XP, but then I tried Windows 7 for the last couple of days and will simply NEVER go back to XP again..

    Besides, if you're gonna do SSD, Windows 7 is the way forward. XP will be obsolete, like Red Hat 5 and Windows 98SE. Do you really want to risk your data or latest gadget to fail?

    Win 7 vs XP:
    * Better looking
    * Fast
    * More options, integrated backup, it's a big mess, but most of it works. Yeah, u know the drill by now, but it *mostly* works, most of the time, and then it's "good enuff"
    * More integrated recovery tools. More chances of getting back up and running..
    * More robust, flexible & userfriendly install. Not as good as Ubuntu, but better than last time.
    * Support
    * SSD support without all the headaches necessary on XP & Vista. If you're like me, you don't want your drive to die in its infancy..
    * non-admin accounts works
    * UAE security, and no, it's not as annoying as on Vista
    * Better driver support than Vista, runs newer hardware without slipstreaming tons of drivers
    * More native drivers available on Windows Update
    * DX11

    Not a quantum-leap, but Windows 7 fixes most nuances with Vista, and has more OPTIONS ;-)
    XP is already obsoleted by Windows 7 IMHO.

    Face it, XP is dying ;-)

    1. Re:XP? Forget XP! by nschubach · · Score: 3, Insightful

      We all have our different opinions. I've had Windows 7 for a little over a month now and I still find hacks to revert some things back to the way XP did it.

      * Reverted the "breadcrumb" address bar
      * Removed libraries
      * Flexible/robust install? I had no options during mine... There was basically a button that said "Install."
      * Had to remove the search box from Window header, wish I could remove/move the rest
      * Had to edit windows resource files to remove that stupid "command bar" with the organize/etc.
      * Installed Classic Shell to get my treeview lines back. Classic start menu was a bonus.
      * Had to clean up 15 or so folder shortcuts that didn't point to anything in my "user" folder.
      * Had to download a tweak program to remove the horrendously huge borders. Found out theme editing is a PITA, even with a program made for it. Wanted to reduce the button sizes. Couldn't find a decent theme out there.
      * Still hate going into the control panel. Try to manage things in "Computer" / Right-Click Manage so I don't have to go to the control panel.
      * Notice no real speed difference. (Seriously... I had XP installed to burn in my system, then switched to Win7...) SSD performs great on both systems.
      * I spent well over 10 times as much time making Windows 7 close to how I wanted it, XP was a breeze and two registry entries. Windows 7 is going on 10 registry edits + resource hacking + disabling so many services... I'm still not done.
      * The only thing I like about Windows 7 so far is the >4G RAM support without crazy settings and limits.
      * If you know how I can change the file click rename timing (or reverting back to the old file selection look and feel), I'd love to know it. I hate clicking on a file and hitting delete to have windows interpret that as me wanting to delete the filename.
      * As a gamer, I can't think of any games I've played that use DX11... or even 10 for that matter. Then again, there's been a terrible slump in games that excite me recently so I haven't been playing as much as I used to.
      * I'm sure there's more...

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    2. Re:XP? Forget XP! by mjwx · · Score: 2, Insightful

      * Better looking

      Debatable. I prefer XP's minimalist looks.

      * Fast

      Bollocks to that. I went from XP to 7 at work and now having 2 VM's running at once makes my entire system chug (E6600, 4 GB RAM, 2 windows VM's should run fine). 7 is only fast if you're doing nothing with it, utter shite resource management.

      * More options,

      If I want to change my network settings I have to navigate through 7 "helpful" windows wizards before being able to manually set my IP address. No Windows, I dont need you to diagnose the problem, I know the problem. What's that, you want me to contact my Systems Administrator, I AM THE SYSTEMS ADMINISTRATOR.

      * More robust, flexible & userfriendly install.

      Nothing wrong with the Windows 7 install, apart from the fact it installs Windows 7.

      * Support

      Clearly the GP has never tried to contact Microsft support. As an enterprise customer they've been nothing but useless.

      * UAE security

      Well you may consider United Arab Emirates security to be good but it's not what I look for in an OS. Introducing Windows Dubai, Burka edition.

      it's not as annoying as on Vista

      Its just as annoying, the only differnce is I can copy a file with just one UAC popup, not three. Still occurs far too often and takes over whatever I am doing.

      * Better driver support than Vista

      Win 7 default drivers for Asus and Gigabyte motherboards are atrocious, if they haven't published drivers for Vista or 7 for your board forget about upgrading.

      Now for the problems

      * Uses more system resources. Running VMware or playing games is severely affected.
      * USB Storage is more painful. Not just the "scan and fix" dialouge with each USB Drive but I installed the Android SDK and now it refuses to recongise my milestone as a Mass Storage device (only computer in the lab that does this)
      * UI demands more attention, default settings are painful.
      * Important system config utilities are hidden behind bad and useless wizard.

      If they can get DX 11 working OK on Linux, I'll ditch Windows 7.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    3. Re:XP? Forget XP! by Carewolf · · Score: 2, Interesting

      That doesn't seem that different, even back with Windows 2000 started the standard post-install/reinstall procedure:
      * Folder tweaking (show hidden files, file extensions, otherwise it was impossible to see if something was an executable, icon or whatever)
      * TweakUI to improve responsiveness of the UI (this is an official Microsoft tool though, just not shipped with OS).
      * Registry tweaking (In win2k and winxp only to disable auto-loading of all useless services installed by required crapware like DVD-players, file archives, PDF readers, etc.)
      * Enabling useful "eye-candy" (font antialiasing, and more), disable useless eye-candy (oversized borders, slow animations, etc).

      So nothing much changed, it only got slightly worse.