The time differential is completely overshadowed by the difference in functionality, and you need to factor in both the positives *and* the negatives -- assuming you *want* to make a valid comparison.

15 years in tech is an eternity regardless of the decade.

Some "eternities" are a hell of a lot shorter than others. And some arguments are a hell of a lot weaker than others. o.O

yeah... i am still waiting for you to actually make one instead of insulting however you are addressing.

Fix'd your post for you, m8.

You're welcome.

Because if I understand the reason for the incompatibility to begin with then it's more underlying that that. Microsoft have done a ton of architectural changes over the years. Because of this just the mere act of using Microsoft's modern compilers (which turn readable code into machine code) adds dependencies on these architectural changes. Those changes have been backported into Windows 7, 8.x and various Server operating systems, but not to XP and Vista due to their end-of-life support having expired.

For example, that solution of yours would most likely not even work since it still requires that the DLL file can be read and executed, which it can't on unsupported operating systems that can't handle the new dependencies.

As I previously mentioned there's ways around the issue, but all of those comes with a cost that simply doesn't pay for itself.

For example, we can assume that all GOG developers uses modern tools, right? However Fallout: New Vegas isn't a modern game, is it? So even if they attempt to change the source code of the game (which they must do to convert the Steam functionality into Galaxy functionality) then they most likely must import the codebase into a modern toolkit that it simply weren't designed for, which means changes will occur simply by the act of importing it.

The codebase was probably built using an older version of the Windows SDK, of which there's compatibility caveats of having multiple versions installed of (not to mention that few modern development tools are even tested or officially support outdated legacy SDKs). Hell, it's even built using DirectX 9, which is a part of the legacy DirectX SDK which haven't received an update since 2010 (and is therefor not officially supported on Windows 10 either).

The game and the source code for it is simply old. "Supporting" it fully without adding additional dependencies requires that all the development, compiling and testing are done on machines that match the original dependencies of the codebase. Then they also need to test it thoroughly on modern software to ensure that the old dependencies doesn't break anything. And even then they're at the mercy of Microsoft's whims, who can at any moment release another Windows 10 update that might break some of that old dependencies.

Old games that simply needs a wrapper or emulator around it (DOSBox, dgVoodoo, etc) is "simple" to fix since the actual source itself is untouched. But games that originally was built with other integrations (such as the Steam API in this case) either requires an excessively amount of time to reverse engineer the Steam API and implement a wrapper for it that translates inbetween Galaxy and the game (and even then we have the DLL incompatibility issue if the DLL file were compiled with a modern toolkit) or it requires actual changes in the source code of the game, and a recompile of the game itself, which will most likely mean modern tools aka modern dependencies.

There's no simple solution here. It's a highly complex issue that any solution of will have a cost attached to it. The most cheap option is to simply not support those OSes any longer, and therefor not even care about them when translating the game into being playable on modern hardware with modern features (Galaxy integration).

You are speaking from the perspective of a third-party with absolutely no responsibility at all. See my previous post on this matter.

The community can provide unofficial fixes however they want with no warranty or guarantee attached to them. GOG can not. That "extremely simple workaround" you speak of haven't gone through GOG's quality assurance testing at all, so there's no telling what issues it might cause with the game. If GOG would be providing it as a fix then they would basically be taking responsibility for it as well, including whatever issues it might cause for their end-users.

That's the whole gist of my posts. Stop seeing this issue as a random unattached idiot online and start seeing it from a business perspective with all that it entails (QA testing, support, responsibility, continuous development etc). Either do that or I'm going to assume I'm wasting my time discussing with a kid with no knowledge or experience of how the real world and consumer <-> corporation relationships work all across the world.

Speaking on the broader issue to which the thread sort of morphed into. I should have stated that so as not to confuse the two issues: the specific game in question, and the broader matter of continuing support for running games on an older OS, just as they were sold by the store originally.

This. I too am relying on my XP machine to play games I purchased on GOG when they were promised to work on that OS. If via update XP compatibility gets broken, older versions available would solve that issue. I cannot fathom why GOG doesn't offer these.

It'd be handy just in general, for all games and customers. Would be a customer-friendly move that could generate a fair bit of goodwill.

Absolutely. I know it would put my mind at ease and it wouldn't GOG cost anything much, since - like you already pointed out - the old installers exist.

As it stands I'm seriously pondering making my last few purchases, downloading all my games and be done with buying on here.

Just because you want to keep using an OS that is far past its prime does not mean others want to support it. XP had its day in the sun. I hope if you are using XP you are keeping it off any network.
Would you expect Linux distros that have not used Kernel 2.0.x in years to still be serviced or for applications to still work on them? It sounds like you are wanting to take your ball and go home. I say just voice your request like so many others do and stop trying to have the attitude "It should be my way or I will hold my breath". It is up to you of course. :-)

-Tastymonkey

I couldn't do that without compromising my integrity, which I refuse to do. The "business" perspective of the leet corporations is amoral. I've argued economics for 25 or so years, and run into more than a few who acknowledged that straightaway. It's part and parcel of materialism, and in that world, property takes precedence over people, which I find ghastly and offensive. I know *exactly* how the real world works, and consciously choose to deal with it on *my* terms, rather than it's own.

That said, what you claim is again false. GOG could provide the workaround without accepting responsibility by means of a disclaimer. End of.

You realize capitalism and consumerism are what make the 'gaming industry' even possible right? Seems kinda foolish to dig your heels in "on principle"... when you are focusing on frivilous entertainment products made possible by the system you vehemently despise.