Posted December 15, 2015
It makes sense to not purposefully remove features/functionality to cause an application to no longer function on an older OS like Windows XP unless there is a lot to be gained by introducing such changes. For the most part that's not likely to be the case for something like this though.
What a lot of people may not realize though too is that software development teams have finite resources both financial and manpower relted, as do quality assurance testing teams, technical support teams and other aspects of the whole software R&D and support ecosphere. As such every software company has to look at the goals they wish to achieve and how the may best allocate their resources to do so, and when it comes to backwards compatibility related issues of this nature then the percentage of affected customers needs to also be taken into account when making decisions of this sort of nature.
The problem with Windows XP is not only that it is no longer supported by Microsoft officially (regardless of whether there are unofficial ways to still get updates for it through trickery), but that the number of users still using Windows XP is on a sharp declining trajectory and any efforts expended in manpower to maintain or develop new support for it in existing products and upcoming features end up having a larget and larger burden on finite resources compared to the amount of people that benefit from the results. This will only continue to be more pronounced as time goes on too as people will end up needing to move off of XP more and more quickly moving forward due to a number of technical shortcomings of the OS.
One such example is that the web is very quickly moving forward with mass encryption adoption, and while it's only at a slow trickle right now, projects like the lets-encrypt project hope to work towards an always-encrypted Internet for all sites and services. That wont happen overnight of course, but it is certainly starting now, and the entire premise is backed by industry giants including Google, Facebook, Microsoft, Mozilla, Akamai, and many others, a number of whom are directly supporting the letsencrypt project and other efforts underway.
"How does this affect Windows XP?" one might ask. Well, the problem is that the SSL/TLS stack in Windows XP is very ancient and does not support new encryption ciphers that are becoming increasingly common online now, it does not support SHA256 SSL certificates and the entire web is moving away from SHA1 completely. Within less than a year Firefox, Chrome, IE and other major browsers and mobile devices will no longer support SHA1 and that frees websites and other service operators from having to continue supporting this insecure solution. In addition to this, the majority of current generation and several generation old operating systems, web browsers, mobile devices and other software all support SNI, which is a web server/browser feature that allows many websites to be served on a single webserver with one IP address over SSL. SNI has been around forever now but has not really been able to be used due to lack of support for it in Windows XP, old versions of Java and old mobile devices and other ancient software/hardware, but that is changing quickly now and many websites are now rolling out SSL-only and using SNI because the number of people accessing those sites using Windows XP and other legacy technologies that do not support these features are sufficiently small enough that they're able to write them off now. That varies from site to site, the nature of the site and its business model (if any) and the particular types of users that particular site receives and isn't a blanket statement. It just means that SNI is becoming a more widely accepted technology and it is being rolled out there for real now, and that means those sites will not be easily available to Windows XP users.
What does this all have to do with GOG Galaxy? Well it's simple, everyone uses the web and relies upon it, and when important websites are no longer usable in your web browser such as for example because you are using IE6 on Windows XP, then you have no real other option than to upgrade to an OS/software combination that allows you to still do online banking and other functions you need to do. Since this is going to become much more common in the next 12 months as the 3 major browser vendors remove support for SHA1 and website operators roll out sites using SNI in order to fit more websites on a single IP address due to IPv4 being currently exhausted, we can expect that the majority of people using XP will have no choice but to upgrade one way or another whether they like it or not, or else have a non-functional Internet experience.
There are other technologies aside from those I've mentioned here which likewise Windows XP is unable to deal with. Some of these limitations are just inherent in the OS itself, while others are just limitations of Internet Explorer. In some cases, using 3rd party software might allow someone to work around an issue, but in a lot of cases the 3rd party software alternatives no longer support XP either and one would have to use software that itself is insecure. Either way, everyone using XP is being funneled to upgrade to something newer as soon as possible due to its extreme obsolescence that will become more and more visible to users still using it over time.
While the users of these systems are not always aware of this level of technical detail, and probably wouldn't understand it for the most part if it is explained to them, the problems are real and the momentum is underway and can't really be stopped. Companies that design software know all of this, and they realize that come a year and a half from now, the percentage of people still using XP is likely to be incredibly small, probably less than 1% globally if not a magnitude smaller than that. It just does not make sense to commit any serious amount of engineering manpower or financial investment into developing for an unsupported legacy system that barely has a pulse left and more or less just got told that it has terminal cancer figuratively speaking.
Nobody likes to embrace death, but even software dies sometimes and needs to be replaced. It is not always a pleasant experience, and I don't personally favour being forced to do it myself either, but it is a necessity from time to time nonetheless. So I empathize with those who don't want to see XP just drop dead on them, but unfortunately the writing is on the wall and nothing can stop it from happening. Clinging onto it with both hands in a death grip wont save XP, and wont convince any software companies to continue to support it in perpetuity. It's just not viable. I know this may be painful for many to read, but the truth is sometimes not easy to swallow. I had to go through this process myself moving from XP to Windows 7 3 years ago roughly, but once it ended up being relatively painless in the end and worth the change. People shouldn't feel they have to upgrade unnecessarily either, but in this case specifically it really is necessary and will become more apparent to everyone with every month that passes leading through 2016.
Sometimes embracing change is a lot less painful than holding on to it forever, and IMHO this is one of those times.
What a lot of people may not realize though too is that software development teams have finite resources both financial and manpower relted, as do quality assurance testing teams, technical support teams and other aspects of the whole software R&D and support ecosphere. As such every software company has to look at the goals they wish to achieve and how the may best allocate their resources to do so, and when it comes to backwards compatibility related issues of this nature then the percentage of affected customers needs to also be taken into account when making decisions of this sort of nature.
The problem with Windows XP is not only that it is no longer supported by Microsoft officially (regardless of whether there are unofficial ways to still get updates for it through trickery), but that the number of users still using Windows XP is on a sharp declining trajectory and any efforts expended in manpower to maintain or develop new support for it in existing products and upcoming features end up having a larget and larger burden on finite resources compared to the amount of people that benefit from the results. This will only continue to be more pronounced as time goes on too as people will end up needing to move off of XP more and more quickly moving forward due to a number of technical shortcomings of the OS.
One such example is that the web is very quickly moving forward with mass encryption adoption, and while it's only at a slow trickle right now, projects like the lets-encrypt project hope to work towards an always-encrypted Internet for all sites and services. That wont happen overnight of course, but it is certainly starting now, and the entire premise is backed by industry giants including Google, Facebook, Microsoft, Mozilla, Akamai, and many others, a number of whom are directly supporting the letsencrypt project and other efforts underway.
"How does this affect Windows XP?" one might ask. Well, the problem is that the SSL/TLS stack in Windows XP is very ancient and does not support new encryption ciphers that are becoming increasingly common online now, it does not support SHA256 SSL certificates and the entire web is moving away from SHA1 completely. Within less than a year Firefox, Chrome, IE and other major browsers and mobile devices will no longer support SHA1 and that frees websites and other service operators from having to continue supporting this insecure solution. In addition to this, the majority of current generation and several generation old operating systems, web browsers, mobile devices and other software all support SNI, which is a web server/browser feature that allows many websites to be served on a single webserver with one IP address over SSL. SNI has been around forever now but has not really been able to be used due to lack of support for it in Windows XP, old versions of Java and old mobile devices and other ancient software/hardware, but that is changing quickly now and many websites are now rolling out SSL-only and using SNI because the number of people accessing those sites using Windows XP and other legacy technologies that do not support these features are sufficiently small enough that they're able to write them off now. That varies from site to site, the nature of the site and its business model (if any) and the particular types of users that particular site receives and isn't a blanket statement. It just means that SNI is becoming a more widely accepted technology and it is being rolled out there for real now, and that means those sites will not be easily available to Windows XP users.
What does this all have to do with GOG Galaxy? Well it's simple, everyone uses the web and relies upon it, and when important websites are no longer usable in your web browser such as for example because you are using IE6 on Windows XP, then you have no real other option than to upgrade to an OS/software combination that allows you to still do online banking and other functions you need to do. Since this is going to become much more common in the next 12 months as the 3 major browser vendors remove support for SHA1 and website operators roll out sites using SNI in order to fit more websites on a single IP address due to IPv4 being currently exhausted, we can expect that the majority of people using XP will have no choice but to upgrade one way or another whether they like it or not, or else have a non-functional Internet experience.
There are other technologies aside from those I've mentioned here which likewise Windows XP is unable to deal with. Some of these limitations are just inherent in the OS itself, while others are just limitations of Internet Explorer. In some cases, using 3rd party software might allow someone to work around an issue, but in a lot of cases the 3rd party software alternatives no longer support XP either and one would have to use software that itself is insecure. Either way, everyone using XP is being funneled to upgrade to something newer as soon as possible due to its extreme obsolescence that will become more and more visible to users still using it over time.
While the users of these systems are not always aware of this level of technical detail, and probably wouldn't understand it for the most part if it is explained to them, the problems are real and the momentum is underway and can't really be stopped. Companies that design software know all of this, and they realize that come a year and a half from now, the percentage of people still using XP is likely to be incredibly small, probably less than 1% globally if not a magnitude smaller than that. It just does not make sense to commit any serious amount of engineering manpower or financial investment into developing for an unsupported legacy system that barely has a pulse left and more or less just got told that it has terminal cancer figuratively speaking.
Nobody likes to embrace death, but even software dies sometimes and needs to be replaced. It is not always a pleasant experience, and I don't personally favour being forced to do it myself either, but it is a necessity from time to time nonetheless. So I empathize with those who don't want to see XP just drop dead on them, but unfortunately the writing is on the wall and nothing can stop it from happening. Clinging onto it with both hands in a death grip wont save XP, and wont convince any software companies to continue to support it in perpetuity. It's just not viable. I know this may be painful for many to read, but the truth is sometimes not easy to swallow. I had to go through this process myself moving from XP to Windows 7 3 years ago roughly, but once it ended up being relatively painless in the end and worth the change. People shouldn't feel they have to upgrade unnecessarily either, but in this case specifically it really is necessary and will become more apparent to everyone with every month that passes leading through 2016.
Sometimes embracing change is a lot less painful than holding on to it forever, and IMHO this is one of those times.