OpenGL 3 & DirectX 11: The War Is Over


Recommended Posts

(For images, please see the web site....)

Introduction

Given the prevalence of DirectX nowadays, we tend to forget that 10 years ago an all-out war was being waged between Microsoft and Silicon Graphics in the field of 3D APIs. The two companies were both trying to win over developers, with Microsoft using its financial muscle and SGI relying on its experience and its reputation in the field of real-time 3D. In this modern David-versus-Goliath battle, the “little guy” won a precious ally in one of the most famous game developers–-Mr. John Carmack. In part due to the success of the Quake engine, solid support for OpenGL opengl became important enough to motivate makers of 3D cards to provide complete drivers. In fact, it gave 3dfx one of its early advantages and knocked ATI to the back of the pack as it struggled with its OpenGL support.

Meanwhile, Microsoft was starting from scratch, and the learning curve was steep. So, for several years, Direct3D direct3d ’s capabilities were beyond the curve, with an interface that many programmers found a lot more confusing than OpenGL’s. But nobody can accuse Microsoft of being easily discouraged. With each new version of Direct3D, it gradually began to catch up with OpenGL. The engineers in Redmond worked very hard to bring performance up to its rival API’s level.

A turning point was reached with DirectX 8, released in 2001. For the first time, Microsoft’s API did more than just copy from SGI. It actually introduced innovations of its own like support for vertex and pixel shaders. SGI, whose main source of revenue was the sale of expensive 3D workstations, was in a bad position, having failed to foresee that the explosion of 3D cards for gamers would prompt ATI and Nvidia nvidia to move into the professional market with prices so low (due to economies of scale) that SGI couldn’t keep up. OpenGL’s development was also handicapped by bitter disputes among its proponents. Since the ARB—the group in charge of ratifying the API’s development—included many different, competing companies, it was hard to reach agreement on the features to be added to the API. Instead, each company promoted its own agenda. Conversely, Microsoft was working solely with ATI and Nvidia, using its weight to cast a deciding vote if there was disagreement.

With DirectX 9, Microsoft managed to strike a decisive victory, imposing its API on developers. Only John Carmack and those who insisted on portability remained faithful to OpenGL. But their ranks dwindled. And yet a reversal of fortunes was still possible. It had happened with Web browsers, after all. Even when a company has maneuvered itself into a near monopoly, if it rests on its laurels, it’s not all that rare for a competitor to rise from his ashes. So when the Khronos group took over OpenGL two years ago, many hopes were rekindled with all eyes on the upcoming SIGGRAPH conference that year.

Last month, Khronos was to have announced OpenGL 3, a major revision of the API that’s supposed to catch up with Microsoft, which was also scheduled to launch its next-gen DirectX 11 API. But things didn’t really go as planned.

<snipped - see source for rest of article>

Source: tom's hardware

Edited by PureLegend
Link to comment
https://www.neowin.net/forum/topic/670942-opengl-3-directx-11-the-war-is-over/
Share on other sites

Until Microsoft releases their method on other platforms (or at least opens it up so it can be freely implemented by others who want to port it), it is OpenGL for me.

which they wont ..... they rather customer keep buying windows for DirectX upgrades/update ... for short windows exclusive and will stay that way .

what we call it ? oh yes locking in customers

which they wont ..... they rather customer keep buying windows for DirectX upgrades/update ... for short windows exclusive and will stay that way .

what we call it ? oh yes locking in customers

I call it business.

It's a better read on Tom's Hardware. It's not just a wall of text, and there are pretty pictures to help visualise wtf they're talking about.

That is why I posted the following at the top of the story:

(For images, please see the web site....)

Of course, you completely failed to see that; typical!

It's not about how pretty it is or how convenient it is for you, it's about the ad-revenue you're taking away from the original source.

Funny, but it is standard practice in the Breaking News section to post the content with a link.

Most of the time, it is complete text content, so no need singling out this specific post, or the thread starter. A discussion of this sort would need to be with Neowin Staff who set the rules and accepted practices.

That is why I posted the following at the top of the story:

(For images, please see the web site....)

Of course, you completely failed to see that; typical!

I didn't fail to see it at all. Just making a statement.

I my opinion, you'd have been better off just posting the title, a small portion of the text, and a link.

Copy and pasting from 10 pages seems like a bit of a waist of time.

But honestly, thanks for sharing, it was an interesting read.

Funny, but it is standard practice in the Breaking News section to post the content with a link.

Most of the time, it is complete text content, so no need singling out this specific post, or the thread starter. A discussion of this sort would need to be with Neowin Staff who set the rules and accepted practices.

Actually, the standard practice is to post a snippet along with a link to the full article.

That's because most of the time the complete text is only a paragraph or two. An article of this length should not be copied. Actually there is no singling out here. It doesn't matter who posts it but an article of this length should not be copied in it's entirety. If you don't see the problem with doing that, then I'm sorry I can't help you.

As for Neowin Staff, it's up to them to do their jobs. All I can do is click the happy little 'report' button. Or maybe bring this to the attention of those who care... ;)

Actually, the standard practice is to post a snippet along with a link to the full article.
A check of the 10 next "Breaking News" threads, not counting this full cut/paste has the results of:

Full Text: 4

Partial Snip: 3

Spam for software: 1

Site Blocked for me at work: 1 (gee, a full text would be helpful in that case)

Youtube link (why is that news?) but also blocked: 1 (And that, apparently is in French, anyhow, judging by the comments posted)

Seems that there is no real "standard", except to allow both full and snippet type of Breaking News. ;)

That's because most of the time the complete text is only a paragraph or two. An article of this length should not be copied. Actually there is no singling out here. It doesn't matter who posts it but an article of this length should not be copied in it's entirety. If you don't see the problem with doing that, then I'm sorry I can't help you.
Agreed that the article was overly lengthy. However, some people read Neowin News at work during lunch and breaks. In cases where the destination site is blocked, a full-text is an advantage.
As for Neowin Staff, it's up to them to do their jobs. All I can do is click the happy little 'report' button. Or maybe bring this to the attention of those who care... ;)
Report away. You want the staff do to their jobs? Then stop whining about it in the threads and use the report and let them decide. :whistle:
A check of the 10 next "Breaking News" threads, not counting this full cut/paste has the results of:

Full Text: 4

Partial Snip: 3

Spam for software: 1

Site Blocked for me at work: 1 (gee, a full text would be helpful in that case)

Youtube link (why is that news?) but also blocked: 1 (And that, apparently is in French, anyhow, judging by the comments posted)

Seems that there is no real "standard", except to allow both full and snippet type of Breaking News. ;)

And does that make it okay? Certainly not. Just because you see it happening a lot does not make it acceptable, no, it's actually just indicative of careless staff. ;)

Agreed that the article was overly lengthy. However, some people read Neowin News at work during lunch and breaks. In cases where the destination site is blocked, a full-text is an advantage.

In that case, they can either: 1) Choose to abide by their employer's decisions and actually do what they're paid to do and wait till they get home to read the article or 2) Read the snippet and still participate in the discussion just fine

The bottom line is, full-text is a disadvantage to the people who work hard on putting these articles together to generate ad revenue for their site. Are you an advocate of piracy? This really isn't that far off it.

Report away. You want the staff do to their jobs? Then stop whining about it in the threads and use the report and let them decide. :whistle:

Haha, I'm sorry, but who's the one whining? :rolleyes:

---

Anyway, that's the last I'll discuss on this in this topic as it is offtopic. I'm sure you probably have a hard time realizing why this is an issue because either you don't really understand the implications or just don't care.

And does that make it okay? Certainly not. Just because you see it happening a lot does not make it acceptable, no, it's actually just indicative of careless staff. ;)
I said "standard practice", meaning it is common and accepted. You are now discussing if it is piracy and right. Nice bait-and-switch in a discussion. :p
Haha, I'm sorry, but who's the one whining? :rolleyes:
Who? You.
Umm... can we not copy and paste the full article here? :rolleyes:
It's not about how pretty it is or how convenient it is for you, it's about the ad-revenue you're taking away from the original source.
...

That's because most of the time the complete text is only a paragraph or two. An article of this length should not be copied. Actually there is no singling out here. It doesn't matter who posts it but an article of this length should not be copied in it's entirety. If you don't see the problem with doing that, then I'm sorry I can't help you.

...

hmm well the PC has little to do with gaming now anyway. developers are just going to use whatever API is used on consoles and then port to PC. so i would imagine developers will move to DX11 or 12 or whatever when the xbox 720 comes out. and thus if people want to play those newest games on PC they will have to have windows vista or later. by which time most people will.

hmm well the PC has little to do with gaming now anyway. developers are just going to use whatever API is used on consoles and then port to PC. so i would imagine developers will move to DX11 or 12 or whatever when the xbox 720 comes out. and thus if people want to play those newest games on PC they will have to have windows vista or later. by which time most people will.

The PC is still the largest gaming platform....

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!